refactor: resource removal wait and additional info changes - #485
Draft
shreddedbacon wants to merge 6 commits into
Draft
refactor: resource removal wait and additional info changes#485shreddedbacon wants to merge 6 commits into
shreddedbacon wants to merge 6 commits into
Conversation
shreddedbacon
changed the title
shreddedbacon
force-pushed
the
wait-deletion
branch
from
April 23, 2026 00:15
d51e55f to
7c390f4
Compare
shreddedbacon
force-pushed
the
wait-deletion
branch
from
June 10, 2026 22:33
7c390f4 to
7429631
Compare
shreddedbacon
force-pushed
the
wait-deletion
branch
from
July 22, 2026 03:22
b539947 to
737bfb4
Compare
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
2 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.
Just a small refactor to wait for resources to be removed before continuing. This allows for the resources to be removed before the final state collection runs to ensure that the latest state is saved into the services config map
Additional changes to volume information too to reflect changes coming in the API to support volumes on environments.