Orphan mitigation for instances/bindings in state "create failed" #3973
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.
When a creation of a service instance times out and state is create failed, service broker may have kept some metadata, which should be deleted. Therefore adding an orphan mitigation when service instance creation job runs in a timeout and create has state failed.
A short explanation of the proposed change:
Adding an orphan mitigation when service instance creation job runs in a timeout and create has state failed
An explanation of the use cases your change solves
When a creation of a service instance times out and state is create failed, service broker may have kept some metadata, which should be deleted.
I have reviewed the contributing guide
I have viewed, signed, and submitted the Contributor License Agreement
I have made this pull request to the
main
branchI have run all the unit tests using
bundle exec rake
I have run CF Acceptance Tests