You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 15, 2022. It is now read-only.
As an operator, I would like to be able to specify a development branch of a component helm chart repo so that I can test changes to the helm charts before PRing them to the master branch.
In support of this, add a branch field to the component config spec such that I can override which branch each subcomponent definition or helm chart is cloned from per environment.
A possible work-around could be to maintain a separate HLD repository (and its target manifest repo) that references the development branch(es) instead of the master branch(es), but that feels like it would defeat the beauty of the bedrock framework.
The text was updated successfully, but these errors were encountered:
As an operator, I would like to be able to specify a development branch of a component helm chart repo so that I can test changes to the helm charts before PRing them to the master branch.
In support of this, add a branch field to the component config spec such that I can override which branch each subcomponent definition or helm chart is cloned from per environment.
example config/test.yaml:
A possible work-around could be to maintain a separate HLD repository (and its target manifest repo) that references the development branch(es) instead of the master branch(es), but that feels like it would defeat the beauty of the bedrock framework.
The text was updated successfully, but these errors were encountered: