clean service counters and env counters when deleting project#4743
Merged
leozhang2018 merged 1 commit intoJun 18, 2026
Merged
Conversation
Signed-off-by: Cynthia <chenchen@koderover.com>
PetrusZ
approved these changes
Jun 16, 2026
huanghongbo-hhb
approved these changes
Jun 16, 2026
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
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.
What this PR does / Why we need it:
Previously, env service version counters and service template revision counters could remain in the
countercollection after project deletion. If a project with the same name was recreated later, these stale counters could affect newly created resources by continuing revisions from deleted project data.What is changed and how it works?
Delete env service version counters after env service versions are removed for the project.
Delete normal and production service template revision counters during async project resource cleanup.
Does this PR introduce a user-facing change?
This change is