Conversation
rashedkvm
force-pushed
the
stack-management
branch
4 times, most recently
from
46b309e to
1a3a7c6
Compare
rashedkvm
force-pushed
the
stack-management
branch
4 times, most recently
from
5fcdfda to
e2fc6df
Compare
rashedkvm
force-pushed
the
stack-management
branch
7 times, most recently
from
aa5f9b9 to
a1eab88
Compare
rashedkvm
force-pushed
the
stack-management
branch
from
a1eab88 to
3b29b53
Compare
4 tasks
Member
|
Thanks for the PR - i adapted the RFC i also think the new state naming fits better 👍🏼 cloudfoundry/community#1405 |
This was referenced Jan 20, 2026
Samze
reviewed
Jan 20, 2026
Contributor
|
PR looks good, I haven't found any issues while testing on a dev environment. Will you create integration tests for all new scenarios? You could add new tests to https://github.com/cloudfoundry/capi-bara-tests. |
rashedkvm
force-pushed
the
stack-management
branch
from
3b29b53 to
12d6773
Compare
Contributor
Author
Thank you and yes I can add test in https://github.com/cloudfoundry/capi-bara-tests |
rashedkvm
force-pushed
the
stack-management
branch
from
12d6773 to
99e4e94
Compare
FloThinksPi
added a commit
to FloThinksPi/community
that referenced
this pull request
Jan 28, 2026
Replaced 'description' field usage with 'state_reason' for better communication of stack states in warning and error messages. Found out its needed during implementation in cloudfoundry/cloud_controller_ng#4712
FloThinksPi
added a commit
to FloThinksPi/community
that referenced
this pull request
Jan 28, 2026
Leverage an additional 'state_reason' field for better communication in warning and error messages related to stack states. Found out its needed in implementation see cloudfoundry/cloud_controller_ng#4712
beyhan
pushed a commit
to cloudfoundry/community
that referenced
this pull request
Jan 28, 2026
Leverage an additional 'state_reason' field for better communication in warning and error messages related to stack states. Found out its needed in implementation see cloudfoundry/cloud_controller_ng#4712
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>
Signed-off-by: Rashed Kamal <rashed.kamal@broadcom.com>
Signed-off-by: Rashed Kamal <rashed.kamal@broadcom.com>
…APIs Sets warnings in the response hash when there are warnings Signed-off-by: Rashed Kamal <rashed.kamal@broadcom.com>
Actions own their warnings and Controllers set warnings → headers 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
117dc31 to
8c312e8
Compare
Samze
reviewed
Jan 28, 2026
Samze
reviewed
Jan 28, 2026
rashedkvm
force-pushed
the
stack-management
branch
from
8c312e8 to
5fea1b7
Compare
Polishing based on review comments Signed-off-by: Rashed Kamal <rashed.kamal@broadcom.com>
rashedkvm
force-pushed
the
stack-management
branch
from
5fea1b7 to
2b79df5
Compare
Samze
previously approved these changes
Jan 28, 2026
Signed-off-by: Rashed Kamal <rashed.kamal@broadcom.com>
Samze
approved these changes
Jan 29, 2026
ari-wg-gitbot
added a commit
to cloudfoundry/capi-release
that referenced
this pull request
Jan 29, 2026
Changes in cloud_controller_ng:
- feat: add 'broker_catalog_ids' filter to /v3/service_offerings endpoint
PR: cloudfoundry/cloud_controller_ng#4805
Author: George Blue <blgm@users.noreply.github.com>
- Stack management
PR: cloudfoundry/cloud_controller_ng#4712
Author: Rashed K <89036140+rashedkvm@users.noreply.github.com>
5 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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