Disable pruning for automated sync of root app#218
Merged
Conversation
This ensures that we'll be able to roll out support for multiple root apps without having to disable auto-sync for the default root app before the roll out, since we already have some configuration that will reassign existing component instances to another root app. Later, we'll want to keep this setting, so we can move component instances between different root apps without having to manually disable auto-sync for the root apps on all clusters that use the component that's being moved.
|
🚀 This PR has been released as Triggering workflows 🛠️ Auto tagging enabled with label |
DebakelOrakel
approved these changes
Dec 31, 2024
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.
This ensures that we'll be able to roll out support for multiple root apps without having to disable auto-sync for the default root app before the roll out, since we already have some configuration that will reassign existing component instances to another root app.
Later, we'll want to keep this setting, so we can move component instances between different root apps without having to manually disable auto-sync for the root apps on all clusters that use the component that's being moved.
Extracted from #216
Checklist
changelog.
The PR has a meaningful description that sums up the change. It will be
linked in the changelog.
bug,enhancement,documentation,change,breaking,dependencyas they show up in the changelog.