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
Is your feature request related to a problem? Please describe.
When there is a git changes triggering bosh cloud-config or runtime-config,,the director is updated, but the related deployments are not deployed
Describe the solution you'd like
For better convergence, it would be usefull to retrigger the bosh deployments after a cloud-config / runtime-config change
Describe alternatives you've considered
document the retrigger all for operators (which defeat the gitops approach of COA)
Is your feature request related to a problem? Please describe.
When there is a git changes triggering bosh cloud-config or runtime-config,,the director is updated, but the related deployments are not deployed
Describe the solution you'd like
For better convergence, it would be usefull to retrigger the bosh deployments after a cloud-config / runtime-config change
Describe alternatives you've considered
document the retrigger all for operators (which defeat the gitops approach of COA)
Additional context
cloud-config and runtime-config are new versionned. There is a concourse resource which migh be usefull as a trigger dependency of all the bosh deployments
https://github.com/cloudfoundry-community/bosh-config-resource
The text was updated successfully, but these errors were encountered: