-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
manage cloud-config / runtime-config change #274
Comments
This resource seems to match requirements for detecting changes (ie To be able to use it as |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: