feat: migrate to AWS SDK v3 with complete feature parity (v4.1.2) #2
Conversation
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
## Description Major version upgrade from v3.4.0 to v4.1.2 migrating from deprecated @auth0/s3 library to AWS SDK v3 while maintaining 100% backward compatibility and adding significant new features and improvements. This addresses the critical dependency update needed for modern AWS SDK support and enhances the plugin with professional-grade tooling and CI/CD infrastructure. ## Type of change - [x] New feature (non-breaking change which adds functionality) - [x] This change requires a documentation update ## Major Features Added ### 🚀 AWS SDK v3 Migration - Complete migration from @auth0/s3 to @aws-sdk/client-s3 - Maintained exact API compatibility with original library - Enhanced error handling and performance optimizations ### 📦 New Functionality - Bucket tags management with merge functionality - Enhanced metadata synchronization capabilities - New CLI commands: s3sync:metadata, s3sync:tags, s3sync:bucket:* - Support for per-bucket operations ### 🔧 Infrastructure Improvements - Complete GitHub Actions CI/CD pipeline - OIDC-based secure NPM publishing - Yarn v4 with modern package management - Automated testing and coverage reporting - Release management scripts ## How Has This Been Tested? - [x] Jest test suite with 24 comprehensive test cases - [x] Feature compatibility tests ensuring backward compatibility - [x] Basic integration tests validating core plugin functionality - [x] AWS SDK v3 compatibility validation - [x] Serverless Framework 3.x and 4.x compatibility testing - [x] Manual testing with real S3 buckets and deployments ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [x] Any dependent changes have been merged and published in downstream modules ## Breaking Changes None - this maintains 100% backward compatibility with existing configurations. ## Dependencies Updated - @aws-sdk/client-s3: ^3.800.0 (new) - @aws-sdk/client-cloudformation: ^3.800.0 (new) - Removed: @auth0/s3 (deprecated) - Updated: All other dependencies to latest secure versions
subodhkarwa
approved these changes
Nov 21, 2025
subodhkarwa
requested changes
Nov 21, 2025
subodhkarwa
left a comment
subodhkarwa
left a comment
There was a problem hiding this comment.
Would be good to have our usual structure
So steps and other things will work as flaconi standards.
You can copy paste remaining files :
https://github.com/Flaconi/monitoring-service/tree/master/.github
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.
Description
Major version upgrade from v3.4.0 to v4.1.2 migrating from deprecated @auth0/s3 library to AWS SDK v3 while maintaining 100% backward compatibility and adding significant new features and improvements.
This addresses the critical dependency update needed for modern AWS SDK support and enhances the plugin with professional-grade tooling and CI/CD infrastructure.
Type of change
Major Features Added
🚀 AWS SDK v3 Migration
📦 New Functionality
🔧 Infrastructure Improvements
How Has This Been Tested?
Checklist:
Breaking Changes
None - this maintains 100% backward compatibility with existing configurations.
Dependencies Updated