s3: Add warning if key ID or secret is empty #3532
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
garrmcnu
added a commit
to garrmcnu/restic
that referenced
this pull request
Sep 30, 2021
MichaelEischer
requested changes
Oct 2, 2021
Also add debug message if no credential types are available. Closes restic#2388
0f1b6e5
to
708d7a2
Compare
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.
What does this PR change? What problem does it solve?
Add warning for S3/GS/Azure if credentials are not set.
Was the change previously discussed in an issue or on the forum?
Closes #2388
Checklist
changelog/unreleased/that describes the changes for our users (see template).gofmton the code in all commits.