razzle
Prev stuffs: https://github.com/defenseunicorns/zarf/pull/833/files https://github.com/defenseunicorns/zarf/pull/431
There has not been a lot of drive for native support for encrypted contents in Zarf. My opinion leaning more towards that secrets should all be ephemeral and runtime generated....
Kicking this down the road to be implemented by OpenSSF @eddiezane FYSA
With the `wait-for` feature completed, I believe this can be safely closed. @Racer159 @jeff-mccoy
Satisfied by https://github.com/defenseunicorns/build-harness
I think the core ask of this feature: > The k3s distro package currently only supports systems with systemd installed (even though k3s does support Alpine/OpenRC) is best solved w/...
I can see a `tech-debt` issue being created for our k3s distro to support more linux flavors.
Partially implemented in: https://github.com/defenseunicorns/zarf/issues/1960 w/ the addition of `zarf tools registry prune`
During `zarf dev find-images` automatically add the digest to any tag to help with pinning resources
Blocked by #2425
Possible duplicate of https://github.com/defenseunicorns/zarf/issues/2313, resolved by https://github.com/defenseunicorns/zarf/pull/2314. Will be included in the next release (v0.32.4+). In the meantime I would downgrade Zarf to v0.32.2 as @daniel-palmer-gu suggested. If you want...