✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Greptile Overview

Greptile Summary

Fixed AWS Secrets Manager sync to properly handle key schemas when using many-to-one mapping behavior. The key changes:

• In many-to-one mode, the key schema is now correctly applied to the secret name itself (not individual keys within the JSON)
• The unmodifiedSecretMap parameter was added to preserve original key names for the JSON value structure
• Early return added in getSecrets to prevent incorrect schema stripping for many-to-one imports
• Extracted getKeyWithSchema utility function for consistent schema application across sync, import, and delete operations

The fix ensures that when using many-to-one mapping with a key schema like {{environment}}_{{secretKey}}, the schema is applied to the AWS secret name (e.g., prod_my-config) while the JSON content maintains the original key names.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The changes are focused and address a specific bug in schema handling for many-to-one AWS Secrets Manager sync. The logic is clear, consistent, and properly handles the distinction between one-to-one and many-to-one mapping behaviors. No security vulnerabilities or breaking changes introduced.
• No files require special attention

Important Files Changed