ArgoCD-free use?

[wokalski]

Bear with me here, and I don't even suggest you implement it @arnarg but my teammates are doing a presentation about nix and k8s and turns out nixidy is the best tool out there for simply declaring k8s manifests.

It's a cosmetic change, but it could be a "declarative" mode where all manifests are output in one directory, no apps are generated and there's a script that simply wraps apply --prune.

I think it could also encourage gradual migration where you start off with nixidy only and you only start using argo when you need it.

[arnarg]

It shouldn't be difficult to make a new build artifact that symlinks all built manifests into a single folder and skips the apps application. A new CLI subcommand could build this.

https://github.com/arnarg/nixidy/blob/main/modules/build.nix

Resources would still need to be defined in applications though, I wouldn't want to change the module options structure for this.

Thanks for the suggestion!

[wokalski]

yes, i agree they should be in applications

[arnarg]

TIL about --prune BTW! It could work well with allow list with a label selector (this new build type could label all resources with some nixidy specific label) or apply set. I think the nixidy command should just run the apply script automatically (unless there's a good reason to just give the user a folder and script instead).

[arnarg]

I've made an initial allowlist based implementation of this in 6db561d.

To try it out you can run nix build .#nixidyEnvs.<system>.<env>.declarativePackage and then run ./result/apply.

[wokalski]

Epic. Forwarded it to my teammates. Will use it for any toy projects.

[arnarg]

I plan on changing it to applyset based purge and will eventually add a CLI subcommand for it, maybe nixidy apply .#<env>.