Skip to content
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(optimus): support multiple namespaces on replay and backup #63

Merged
merged 5 commits into from
Dec 16, 2021

Conversation

arinda-arif
Copy link
Contributor

No description provided.

@arinda-arif arinda-arif marked this pull request as draft November 16, 2021 07:26
@arinda-arif arinda-arif force-pushed the optimus-replay-backup-multiple-namespace branch 3 times, most recently from d79397c to 8f4aa9a Compare November 18, 2021 04:21
@arinda-arif arinda-arif marked this pull request as ready for review November 18, 2021 04:22
@arinda-arif arinda-arif force-pushed the optimus-replay-backup-multiple-namespace branch from 8f4aa9a to e51a370 Compare December 7, 2021 04:36
@kushsharma kushsharma changed the title feat(Optimus): support multiple namespaces on replay and backup feat(optimus): support multiple namespaces on replay and backup Dec 10, 2021
…am and allowed_downstream in replay and backup
@arinda-arif arinda-arif force-pushed the optimus-replay-backup-multiple-namespace branch from e30ef93 to 5b28d20 Compare December 13, 2021 07:32
@@ -773,11 +778,13 @@ message BackupDryRunRequest {
string resource_name = 3;
string namespace = 4;
string description = 5;
bool ignore_downstream = 6;
bool ignore_downstream = 6 [deprecated=true];
repeated string allowed_downstream = 7;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what if we rename it to downstream_namespace_filter? Also add some comments about how this work?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure i can add the comment. for the name, does the concern of naming it allowed_downstream is because it is not clear enough that it is representing namespaces? if yes, does allowed_downstream_namespace sounds better than downstream_namespace_filter? to avoid questions on what is this filter, why it is needed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as discussed, will go with allowed_downstream_namespaces

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hi @kushsharma , have changed to allowed_downstream_namespaces and added the comments. please take a look.

@kushsharma
Copy link
Member

LGTM

@kushsharma kushsharma merged commit 2e379e4 into main Dec 16, 2021
@kushsharma kushsharma deleted the optimus-replay-backup-multiple-namespace branch December 16, 2021 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants