-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(cli): ignore tracking annotation on backup restore #18960
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com>
✅ Preview Environment deployed on Bunnyshell
See: Environment Details | Pipeline Logs Available commands (reply to this comment):
|
✅ Preview Environment created on Bunnyshell but will not be auto-deployedSee: Environment Details Available commands (reply to this comment):
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #18960 +/- ##
==========================================
- Coverage 50.66% 50.66% -0.01%
==========================================
Files 315 315
Lines 43347 43370 +23
==========================================
+ Hits 21963 21974 +11
- Misses 18882 18893 +11
- Partials 2502 2503 +1 ☔ View full report in Codecov by Sentry. |
…/argo-cd into import-without-tracking
Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com>
Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com>
If an argocd instance in namespace X, managed by another argo instance needs to be backed up and restored in namespace Y, also managed as code by a "dr" argo instance, then the tracking annotation will cause OutOfSync and potentially shared resource error.
Solution:
Bonus: