Best practices for changing BOSH property names


Jim CF Campbell
 

In order to prevent build pipeline breaking changes, when changing BOSH
property names it is recommended that:

-

Support both the new and old name “for a while”.
-

Announce breaking change on cf-dev, including what “a while” is.
-

Modify stub manifests on all deployments that you know and care about.
-

After "a while", remove the old property name.




--
Jim Campbell | Product Manager | Cloud Foundry | Pivotal.io | 303.618.0963


Noburou TANIGUCHI
 

:+1:

But I have a question.
If an old property and the corresponding new property have different values,
which one will be used?



Jim Campbell wrote
In order to prevent build pipeline breaking changes, when changing BOSH
property names it is recommended that:

-

Support both the new and old name “for a while”.
-

Announce breaking change on cf-dev, including what “a while” is.
-

Modify stub manifests on all deployments that you know and care about.
-

After "a while", remove the old property name.




--
Jim Campbell | Product Manager | Cloud Foundry | Pivotal.io | 303.618.0963




-----
I'm not a ...
noburou taniguchi
--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-Best-practices-for-changing-BOSH-property-names-tp3819p3829.html
Sent from the CF Dev mailing list archive at Nabble.com.