-
Notifications
You must be signed in to change notification settings - Fork 89
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
[PWX-34991] Fetching rules from migration namespace instead of namespace to migrate #1569
Conversation
Can one of the admins verify this patch? |
ca1a627
to
91657e1
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1569 +/- ##
==========================================
+ Coverage 66.53% 67.49% +0.96%
==========================================
Files 43 43
Lines 5453 5636 +183
==========================================
+ Hits 3628 3804 +176
+ Misses 1491 1490 -1
- Partials 334 342 +8 ☔ View full report in Codecov by Sentry. |
864e52b
to
cacb1b4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
2668539
to
a42fc78
Compare
a42fc78
to
9d080be
Compare
8e7566b
to
8e253ae
Compare
9149cfc
to
848344d
Compare
What type of PR is this?
What this PR does / why we need it:
As part of existing code, when users create migrationschedule and clusterpair in the admin namespace, they have to create preExec and postExec rules in both the admin Namespace as well as the namespaces to be migrated.
We fix this inconvenience by fetching the rules from adminNamespace only.
Does this PR change a user-facing CRD or CLI?:
No
Is a release note needed?:
Yes, TBD
Does this change need to be cherry-picked to a release branch?:
Yes, 23.11.0
Testing Details
Have tested the changes in a local cluster and verified the bug as well as the fix.
Validated the fix by creating the migrationSchedule in the admin namespace and migrating default namespace. For this case the rules had to be created in the admin namespace.