-
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
Remove consistency check on deployment-dependencies.yml#deployment.<dep_name> #150
Labels
Comments
o-orand
added a commit
that referenced
this issue
Jul 6, 2018
We don't remove consistency checks, but it is possible to deactivate it using the `bosh-deployment` generic key. So either a valid `deployment-name` is used, either the generic-key. closes #150
o-orand
added a commit
that referenced
this issue
Jul 6, 2018
We don't remove consistency checks, but it is possible to deactivate it using the `bosh-deployment` generic key. So either a valid `deployment-name` is used, either the generic-key. closes #150
o-orand
added a commit
that referenced
this issue
Jul 9, 2018
We don't remove consistency checks, but it is possible to deactivate it using the `bosh-deployment` generic key. So either a valid `deployment-name` is used, either the generic-key. closes #150
o-orand
added a commit
that referenced
this issue
Jul 9, 2018
We don't remove consistency checks, but it is possible to deactivate it using the `bosh-deployment` generic key. So either a valid `deployment-name` is used, either the generic-key. closes #150
o-orand
added a commit
that referenced
this issue
Jul 9, 2018
We don't remove consistency checks, but it is possible to deactivate it using the `bosh-deployment` generic key. So either a valid `deployment-name` is used, either the generic-key. closes #150
lucaspinto
pushed a commit
that referenced
this issue
Jul 11, 2018
We don't remove consistency checks, but it is possible to deactivate it using the `bosh-deployment` generic key. So either a valid `deployment-name` is used, either the generic-key. closes #150
gberche-orange
pushed a commit
to orange-cloudfoundry/cf-ops-automation-broker
that referenced
this issue
Apr 23, 2021
gberche-orange
pushed a commit
to orange-cloudfoundry/cf-ops-automation-broker
that referenced
this issue
Apr 23, 2021
gberche-orange
pushed a commit
to orange-cloudfoundry/cf-ops-automation-broker
that referenced
this issue
Apr 23, 2021
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.
Currently
deployment-dependencies.yml
enforces the deployment namecf-ops-automation/docs/reference_dataset/template_repository/hello-world-root-depls/bosh-deployment-sample/deployment-dependencies.yml
Lines 2 to 3 in 72958b9
In the context of COAB, this constraint requires a templating of this file, whereas it could be the same among all on-demand service instances sharing a same model. See orange-cloudfoundry/cf-ops-automation-broker#31
Describe the solution you'd like
COA to ignore the deployment name in
deployment-dependencies.yml
and accept such static deployment name below (e.g. for all on-demand service instance deployments)Describe alternatives you've considered
COAB templating
The text was updated successfully, but these errors were encountered: