forked from yugabyte/yugabyte-db
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[BACKPORT 2.7.2][yugabyte#9331] Platform: Allow editing "Configuratio…
…n Name" for backup storage provider without security credentials Summary: Attempts to update backup configurations which have credentials, but without changing them, fail on a step of the credentials check. As example: - S3 storage configuration with valid credentials (the credentials are verified on a stage of the configuration creation); - We are changing only the configuration name; - Save changes -> "Tha AWS Access Key Id you provided does not exist in our records". The fix is to reorder operations: credentials check should go after the passed credentials are unmasked (currently it goes before). Original diff: https://phabricator.dev.yugabyte.com/D12353 Test Plan: Jenkins: rebase: 2.7.2 Test scenario is the same: 1. Create valid S3 configuration, save it. 2. Go to another page and then return back to the S3 backup configuration page; 3. Change the configuration name only and press "Save". Reviewers: hsu, spotachev, amalyshev Subscribers: yugaware, jenkins-bot Differential Revision: https://phabricator.dev.yugabyte.com/D12377
- Loading branch information
1 parent
f103b30
commit b0ae570
Showing
2 changed files
with
55 additions
and
14 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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