razzle

Closing as this should be fixed now in Zarf v0.32.4+

Superceded by #2315

A solid baseline may be https://github.com/Azure/aks-periscope/blob/master/.pre-commit-config.yaml

Can def be split into formatting issues / PRs based upon file type

TODO: - [x] Talk w/ @Racer159 about composition behavior - [x] Discuss `zarf-seed-registry` import behavior - [x] Think about migration behavior - [x] Lint addition? - [x] `zarf package migrate`?

Some final thoughts for review: - Unit testing filters? - `config.CommonOptions.Confirm` behavior w/ `filters.NewDeploymentFilter` - `zarf dev migrate` opinionated YAML transformations - `zarf dev migrate` `RunE` vs `Run` - ADR...

My initial thoughts would be an addition to `make docs-and-schema` to add a `go run main.go internal gen-variables-docs` (or something along those lines)

Finishing this will require takeover of https://github.com/defenseunicorns/zarf/pull/2005

> @YrrepNoj @Racer159 @Noxsios - Requesting the team adds features into the appropriate sections of this list or if there is a better place for this to live then let...

This can safely be closed now that `x-` is allowed in `zarf.yaml`'s schema. Simple usages of YAML anchors like this is a well supported and documented feature of the YAML...