Austin Abro

Hi everyone, I too had a similar case where I didn't want to use https://github.com/xeipuuv/gojsonschema because it seemed unmaintained but I liked the more actionable format for users. I ended...

This looks good to me. Will need approval from @Racer159 @lucasrod16 @Noxsios

@waveywaves You will need to sign your commits. You can follow this guide https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits. You should see verified next to the commit hash in the UI when it's signed successfully.

Hey @waveywaves sorry for the delay but I would like to get this merged in at some point, I think it's pretty close. Could you merge main into this branch?...

Currently the code will output images not marked with the `--why` flag with an empty resources block. I believe the intended behavior is to only show images marked by the...

Another alternative to consider is to introduce an `only.flavors` list key into the zarf schema and deprecating the original `only.flavor`. I believe the comma-separated list makes sense to use on...

After discussions with team, we do not want to move this to a separate common library as both are thin wrappers over more generic widely used packages

LGTM, we will need approval from someone else on the zarf team

Implemented by #2005

Initial approach, - add a command like `zarf prepare validate-schema ` - warn on deploy if the schema isn't right - error on create if the schema isn't right