K8SPSMDB-1035: Allow empty secretName for backup jobs#1377
Merged
hors merged 6 commits intopercona:mainfrom Jan 30, 2024
Merged
K8SPSMDB-1035: Allow empty secretName for backup jobs#1377hors merged 6 commits intopercona:mainfrom
hors merged 6 commits intopercona:mainfrom
Conversation
Collaborator
|
@tadjik1, please sign the CLA |
Contributor
|
@tadjik1 thank you for your contribution. These changes confuse me a little bit because we already should have this functionality and even have a test for it. Could you please share steps to reproduce? @nmarukovich could you please check if this problem is valid? |
egegunes
previously approved these changes
Jan 19, 2024
Contributor
|
@tadjik1 please run gofmt on files you changed |
Collaborator
hors
added a commit
that referenced
this pull request
Jan 25, 2024
Collaborator
Contributor
|
@nmarukovich please review |
Collaborator
commit: eeba153 |
hors
approved these changes
Jan 29, 2024
egegunes
approved these changes
Jan 29, 2024
inelpandzic
approved these changes
Jan 30, 2024
Collaborator
|
Hi @tadjik1 thank you for your contribution. We will include your fix in the next PSMDB release. |
hors
added a commit
that referenced
this pull request
Jan 31, 2024
* K8SPSMDB-1035 test case for #1377 * Update e2e-tests/pitr-sharded/run Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update e2e-tests/pitr-sharded/run Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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
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.
CHANGE DESCRIPTION
Problem:
Empty
secretNameresults in errors in the operator:Cause:
Logic doesn't incorporate possibility of empty secretName which is normal behaviour for the backup jobs running directly on EC2 instances.
https://docs.percona.com/percona-operator-for-mongodb/backups-storage.html
Solution:
Get rid of the log message by ignoring empty secret (do not validate file existence in that case).
I'm extremely new to this project (actually just opened the source code for the first time today), so I'm not sure which Jira ticket needs to be created and whether I need to write tests for this (it seems that tests are missing for this module).
CHECKLIST
Jira
Needs Doc) and QA (Needs QA)?Tests
compare/*-oc.yml)?Config/Logging/Testability