dependency: add OverrideFinalizerName option for deletion guards #627
Conversation
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
Add the ability to override the finalizer name used by a deletion guard dependency. This allows multiple deletion guards for the same resource type to use different finalizers, preventing conflicts when guards have different dependency relationships. This will be needed for the upcoming trunk controller where a port can be both a parent and a subport and we need to differentiate their finalizers.
Collaborator
Author
|
This isn't needed, because we can already pass a different finalizer to the deletion guard. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add the ability to override the finalizer name used by a deletion guard dependency. This allows multiple deletion guards for the same resource type to use different finalizers, preventing conflicts when guards have different dependency relationships.
This will be needed for the upcoming trunk controller where a port can be both a parent and a subport and we need to differentiate their finalizers.