Skip to content

Conversation

@Siumauricio
Copy link
Contributor

…ackup processes

  • Added normalizeS3Path function to standardize S3 path formatting by trimming whitespace and removing leading/trailing slashes.
  • Updated backup-related modules (MySQL, MongoDB, PostgreSQL, MariaDB, and web server) to utilize normalizeS3Path for consistent S3 path handling.
  • Introduced unit tests for normalizeS3Path to ensure correct functionality across various input scenarios.

…ackup processes

- Added normalizeS3Path function to standardize S3 path formatting by trimming whitespace and removing leading/trailing slashes.
- Updated backup-related modules (MySQL, MongoDB, PostgreSQL, MariaDB, and web server) to utilize normalizeS3Path for consistent S3 path handling.
- Introduced unit tests for normalizeS3Path to ensure correct functionality across various input scenarios.
@Siumauricio Siumauricio linked an issue Apr 6, 2025 that may be closed by this pull request
@Siumauricio Siumauricio merged commit 4b51744 into canary Apr 6, 2025
4 checks passed
@Siumauricio Siumauricio deleted the 1588-invalid-behavior-when-using-s3-prefix-destination-for-backups branch April 6, 2025 08:15
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.

Invalid Behavior when using S3 "Prefix Destination" for Backups

2 participants