op-ct
op-ct
@donoghuc https://github.com/halostatue/minitar/pull/42 looks promising
Proposed upstream fix at https://gitlab.sicura.dev/sicura/release-eng/simp-release/-/merge_requests/13
To improve upstream PR responses for [simp/pupmod-puppetlabs-puppet_authorization](https://github.com/simp/pupmod-puppetlabs-puppet_authorization), I'm adopting those to modules into voxpupuli: * https://github.com/voxpupuli/puppet-hocon/pull/1 * https://github.com/voxpupuli/puppet-puppet_authorization/pull/1
> @op-ct Does this need to get resolved for 6.6.0 or can we drop back to the previous release until 6.7.0? We have to drop back. The full resolving suite...
Context: the hocon module is a dependency of simp/pupmod: ``` ├─┬ simp-pupmod (v8.3.1) └─┬ puppetlabs-puppet_authorization (v0.5.1) └── puppetlabs-hocon (v1.1.0) ```
@lmmx: when you get a moment, would you mind reviewing/merging this PR? It's a simple patch, but it closes 4 outstanding issues.
6.6.0 backed out of postgres repo changes, now that 6.6.0 is released new work should incorporate them. This will inevitably lead into updating our puppetdb module, in which case #843...
we have a matrix of GHA-only beaker tests running in GCP. The matrix data is loaded from repo-bound JSON file, which is a.) data-only and b.) now the only unique...