Stack management #4712
Draft
Stack management #4712
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rashedkvm
force-pushed
the
stack-management
branch
3 times, most recently
from
ef8bdb2 to
46b309e
Compare
Signed-off-by: Rashed Kamal <rashed.kamal@broadcom.com>
Signed-off-by: Rashed Kamal <rashed.kamal@broadcom.com>
**V2 API endpoints must not expose or accept state parameter.** Signed-off-by: Rashed Kamal <rashed.kamal@broadcom.com>
Signed-off-by: Rashed Kamal <rashed.kamal@broadcom.com>
Signed-off-by: Rashed Kamal <rashed.kamal@broadcom.com>
Signed-off-by: Rashed Kamal <rashed.kamal@broadcom.com>
and integration into app creation and build workflows. Signed-off-by: Rashed Kamal <rashed.kamal@broadcom.com>
Signed-off-by: Rashed Kamal <rashed.kamal@broadcom.com>
rashedkvm
force-pushed
the
stack-management
branch
from
46b309e to
1a3a7c6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A short explanation of the proposed change:
Implement stack lifecycle management with ACTIVE, DEPRECATED, RESTRICTED, and DISABLED states to enable gradual stack deprecation without causing application downtime.
An explanation of the use cases your change solves
Implement the Stack Management RFC by adding a
statefield to stacks with four lifecycle states: ACTIVE, DEPRECATED, RESTRICTED, and DISABLED. This enables operators to gracefully phase out stacks through lifecycle restrictions rather than causing immediate app downtimeLinks to any other associated PRs
This PR implements RFC #0045.
While the
RESTRICTEDstate is not explicitly defined in the RFC, it is functionally identical toLOCKED. We chose the termRESTRICTEDto prevent any confusion with the existing 'Locked' state used in Buildpacks.I have reviewed the contributing guide
I have viewed, signed, and submitted the Contributor License Agreement
I have made this pull request to the
mainbranchI have run all the unit tests using
bundle exec rakeI have run CF Acceptance Tests