Add backwards-compatibility for restore access key ID env #894
Conversation
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
anothertobi
requested review from
zugao and
lieneluksika
and removed request for
a team
In K8up v1 the env variable `BACKUP_GLOBALRESTORES3ACCESSKEYID` was used and v2 introduced an unintended breaking change of this variable to `BACKUP_GLOBALRESTORES3ACCESKEYID`. Fixes #893 Signed-off-by: Tobi Nehrlich <[email protected]>
zugao
approved these changes
Oct 6, 2023
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.
Summary
In K8up v1 the env variable
BACKUP_GLOBALRESTORES3ACCESSKEYIDwasused and v2 introduced an unintended breaking change of this variable
to
BACKUP_GLOBALRESTORES3ACCESKEYID.Fixes #893
Checklist
For Code changes
bug,enhancement,documentation,change,breaking,dependencyas they show up in the changelog
area:operatorcharts/directory.