Replies: 6 comments 1 reply
-
|
@jpalermo do we want to coordinate and merge all these changes at the same time? Or can this PR: #2345 for example be merged now since it has been reviewed and approved? Keeping it open till April 2022 could result in a big merge conflict down the road. |
Beta Was this translation helpful? Give feedback.
-
|
I don't see any reason to hold anything back. It's more of a goal timeline, not a "we won't remove anything until". Our current belief is that the Registry is no longer needed, so removing any pieces of it should be safe. |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/nouseforaname/bosh-cli/tree/feature/176871612-remove-registry I've been looking at dropping the registry code from the cli as well. |
Beta Was this translation helpful? Give feedback.
-
|
A related documentation update can be found here cloudfoundry/docs-bosh#763 |
Beta Was this translation helpful? Give feedback.
-
|
The registry code from the CLI has been removed and released in v7 of the bosh cli. This breaks usage with a v1 cpi. |
Beta Was this translation helpful? Give feedback.
-
|
registry removed from the agent |
Beta Was this translation helpful? Give feedback.
-
|
registry dropped from bosh codebase |
Beta Was this translation helpful? Give feedback.
-
The registry has been optional and deprecated for a couple of years at this point. We are looking to finish the removal the registry component from the bosh director.
Here is the timeline of what we'd like to do next.
We have verified all current CPIs in bosh-deployment support CPI v2 with the exception of SoftLayer, who communicated they were not interested in supporting CPI v2 currently and are aware of the consequences.
Beta Was this translation helpful? Give feedback.
All reactions