Repository navigation
Enhance stack handling with state_reason field - #1420
Merged
Merged
Conversation
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
approved these changes
Jan 28, 2026
rkoster
approved these changes
Jan 28, 2026
stephanme
approved these changes
Jan 28, 2026
cweibel
approved these changes
Jan 28, 2026
Member
|
Merging because we have quorum and changes are minimal. |
Contributor
|
Looks great, thank you 🥇 |
4 of 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
6 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.
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