GitOps pipeline Update Release Repo step should be able to render manifests present in overrides and update target manifest with rendered file
J
Jasmine green Carp
Currently the GitOPs Update Release Repo step has very limited functionality. You need to declare in the advanced configuration specific values to target for updates. This limits the amount of changes you can easily make within the pipeline. I want to be able to abstract away the full gitops backend from users. I could do this if the Update Release Repo step applied a fully rendered manifest into the target manifest. Overrides already support manifests and we can put values files in overrides that are rendered by the expected hierarchical order and can be used in the K8s Rollout step. If we had this same ability in the Update Release Repo step we would be able to make complex updates to our gitops files totally in harness cleanly.
I'd like to see the ability to have a manifest be rendered at pipeline runtime from manifests present in the overrides and then apply that fully rendered manifest to the target gitops file.
Log In