Skip to content
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

Open
poblin-orange opened this issue Aug 23, 2019 · 1 comment
Open

manage cloud-config / runtime-config change #274

poblin-orange opened this issue Aug 23, 2019 · 1 comment
Assignees

Comments

@poblin-orange
Copy link
Member

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

@o-orand
Copy link
Member

o-orand commented Sep 3, 2019

This resource seems to match requirements for detecting changes (ie in).

To be able to use it as out in our context, currently bosh-config-resource it doesn't not support ops and var files. It should be possible with a PR from EngineerBetter/bosh-config-resource@3839594 to bosh-config-resource

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

2 participants