3 ms·
I keep Yaml/Helm manifests and templates in git so we can track them. Does this support GitOps based workflows?
by verdverm 6y ago
I keep Yaml/Helm manifests and templates in git so we can track them. Does this support GitOps based workflows?
- hustle007 6y agoyes, I would like to know that too
- gscho 6y agoHi! Greg from ShuttleOps here. We currently do not support import of existing YAML and helm manifests but that is certainly on our roadmap
- verdverm 6y agoDo you support maintaining git interoperability, not just importing, but tracking with vcs into the future. Does your tool work with GitOps methodology?
- gscho 6y agoSupporting pre-existing Helm Charts and k8s manifests as artifacts is still on the roadmap, and that needs to be achieved first before we can achieve a GitOps philosophy like Weave Cloud. Ps: Hofstadter looks cool!
- piaste 6y ago> and that needs to be achieved first before we can achieve a GitOps philosophy like Weave Cloud. I think "[automatically] export all generated YAML templates and CLI commands as a git commit / git patch" is something that may be worth supporting even without the import of existing templates. First, it should be much easier, since you're already doing the hard work of generating those strings. Exporting them as a git patch could be as straightforward as keeping an internal repo folder and running git format-patch. Second, it would make for a much easier sell to greenfield projects (which don't need import), because if your GUI tool can export back to the usual YAML code, I might consider using it knowing that I can 'eject' at any time, or that if the generated YAML suffers from any ShuttleOps bugs I can at least fix them and apply the fixed YAML manually while I wait for a bugfix.
- verdverm 6y agoThanks, we use Cuelang as the core UX for a developer focused "high code" paradigm. https://hofstadter.io https://hofstadter.io