un-namespace release_level_backup property
#58
Comments
|
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/151439960 The labels on this github issue will be updated when the story is started. |
|
Resolved in #57 |
|
@zrob there are other unnamespaced job specs in the Line 104 in 7c6ba63 https://github.com/cloudfoundry/cloud_controller_ng/blob/master/bosh/jobs/cloud_controller_ng/spec#L861 Can you please re-open this issue? |
|
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/151765180 The labels on this github issue will be updated when the story is started. |
cf-gitbot
added
unscheduled
scheduled
in progress
delivered
accepted
and removed
accepted
unscheduled
scheduled
in progress
delivered
labels
|
Theses properties will no longer be namespaced in capi-release 1.44. |
ari-wg-gitbot
pushed a commit
that referenced
this issue
Apr 7, 2024
Bump src/code.cloudfoundry.org/tps
dependabot[bot]:
Bump github.com/onsi/gomega from 1.31.1 to 1.32.0 (#58)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks for submitting an issue to
capi-release. We are always trying to improve! To help us, please fill out the following template.Issue
un-namespace
release_level_backuppropertyContext
The
release_level_backupproperty here: https://github.com/cloudfoundry/capi-release/blob/develop/jobs/bbr-cloudcontrollerdb/spec#L19 is currently namespaced with cloudcontroller (job name), probably because it was modelled after the bbr exemplar release.We (bbr) have recently learned that the convention for new job-level properties is for there not to be any namespacing, so we've updated our exemplar release. Could you un-namespace the
release_level_backupproperty in your release?The text was updated successfully, but these errors were encountered: