Fix Invalid credential in backup gateway #4077
Merged
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
minio uses the access and secret key to encrypt its config. We do not need this. We work around this by storing those values in our tmp directory that gets put in the folder. Then, when we start up the backup gateway, we can check for that file. If it exists, we tell backup-gateway that it should use those values. If we were not to do this, then it would be impossible to have 2 automates looking at a shared network drive. This is a best effort thing. If the Invalid credential persists, the best thing that can be done is to turn automate off, remove the .tmp directory in the backups, and turn automate back on. Signed-off-by: Jay Mundrawala <jmundrawala@chef.io>
jaym
force-pushed
the
jdm/backup-gateway-invalid-credentials
branch
from
55cfcd4
to
465461a
Compare
ryancragun
approved these changes
Jul 21, 2020
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.
minio uses the access and secret key to encrypt its config. We do
not need this. We work around this by storing those values in our
tmp directory that gets put in the folder.
Then, when we start up the backup gateway, we can check for that
file. If it exists, we tell backup-gateway that it should use those
values.
If we were not to do this, then it would be impossible to have 2
automates looking at a shared network drive.
This is a best effort thing. If the Invalid credential persists,
the best thing that can be done is to turn automate off, remove the
.tmp directory in the backups, and turn automate back on.
Signed-off-by: Jay Mundrawala jmundrawala@chef.io