Reference the S3 provider compatibility warning from Barman Cloud - #44
Open
josh-heyer wants to merge 1 commit into
Open
Reference the S3 provider compatibility warning from Barman Cloud#44josh-heyer wants to merge 1 commit into
josh-heyer wants to merge 1 commit into
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
Signed-off-by: Josh Heyer <josh.heyer@enterprisedb.com>
Copy link
Copy Markdown
|
any update on this PR ? |
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
|
This must be changed on the main cloudnativepg project @josh-heyer. Happy to do it for you, but I prefer if you get credited for that. Thanks! |
Sorry, something went wrong.
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
Reviewers
At least 2 approving reviews are required to merge this pull request.
3 participants
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.
A colleague had a customer who encountered some issues with a third-party S3 provider; apparently there are a few potential causes for this, but the relevant notes in the Barman docs are a little hard to find (from the CNPG docs).
Something akin to this might also be a useful addition to the equivalent page in the Barman Cloud plugin docs.