"Brew for DevOps"

[RothAndrew]

User feature request, Details TBD - Would love to see a "registry" of common packages that one can deploy, with the ability to host a private registry (because air gap)

[RothAndrew]

Other considerations: How do we make environment-specific configuration (like Big Bang controlPlaneCidr and nodeCidr) configurable so we can make one package that works in different environments?

[RothAndrew]

asking for a place to keep / host / serve pre-built versions of them
this ^

Just like I can do brew install kubectl they'd like zarf deploy doom... or something to that effect

[btlghrants]

Right, gotcha. This is different from "components" because they're all about how the "Zarf Cluster" runs, not so much about the things that "the Zarf cluster" would serve for end users.

[btlghrants]

Seems like a cool idea... but also like it'll require a lot of storage space since we'd basically be storing/re-hosting (potentially) a bunch of copies of repackaged binaries + container images + git repositories + etc. 🤔

[RothAndrew]

The MVP for this could be just the ability to host your own private registry, and then decide if it is worth us hosting a public one (or getting someone else to do it)

[RothAndrew]

But, we can already do a zarf package deploy on remote assets, so that may be sufficient already for this.

[jeff-mccoy]

Closing this older issue now that we have a lot of new capability that with #550 and #621 are merged in.