Skip to content

Conversation

@nastena1606
Copy link
Collaborator

modified: docs/details/minio.md
modified: docs/details/s3-storage.md
modified: docs/details/storage-configuration.md
modified: mkdocs-base.yml

…er what conditions

modified:   docs/details/minio.md
        modified:   docs/details/s3-storage.md
        modified:   docs/details/storage-configuration.md
        modified:   mkdocs-base.yml
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds guidance to help users select the appropriate storage type when configuring Percona Backup for MongoDB with S3-compatible storage services. The changes clarify when to use the s3 storage type versus the minio storage type, addressing potential compatibility issues users may encounter.

  • Added a new "Considerations for choosing a backup storage type" section in the storage configuration overview
  • Added a "When to use the minio storage type" section in the MinIO documentation
  • Updated navigation label from "AWS storage" to "AWS S3 storage" for clarity

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File Description
mkdocs-base.yml Updated navigation label to "AWS S3 storage" for more precise terminology
docs/details/storage-configuration.md Added guidance section explaining when to use s3 vs minio storage types
docs/details/s3-storage.md Removed blank line for formatting consistency
docs/details/minio.md Added detailed section on when to use the minio storage type with troubleshooting tips

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

* [Microsoft Azure Blob storage](azure.md)
* [Alibaba Cloud OSS storage](oss.md)

### Considerations for choosing a backup storage type for s3-compatible storages
Copy link

Copilot AI Dec 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The heading uses lowercase 's3-compatible' which is inconsistent with the capitalized 'S3-compatible' used in the body text. Consider changing to 'S3-Compatible Storages' for consistency and better readability.

Suggested change
### Considerations for choosing a backup storage type for s3-compatible storages
### Considerations for choosing a backup storage type for S3-Compatible Storages

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants