fix: resolve YAML malformation with special character passwords #61
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.
Fixes #14
Describe your changes:
This commit resolves Issue #14 where YAML configuration becomes malformed when passwords contain special characters like quotes, backslashes, or other YAML-unsafe characters, potentially causing deployment failures and security vulnerabilities.
I worked on updating password generation across all modules to use only YAML-safe special characters because the current implementation was generating passwords that could break YAML parsing and cause deployment failures.
Motivation and Context
The random_password resources in modules/rds, modules/opensearch, and airflow_secrets.tf were generating passwords with characters that could break YAML syntax. This created:
This fix ensures all passwords are YAML-safe while maintaining security requirements.
Breaking Changes
None - this is a backward compatible security enhancement.
How Has This Been Tested?
Technical Changes:
Password generation now uses: "!@#$%^&*()-_=+[]{}:?" (excludes quotes, backslashes)
Maintains strong passwords: 16+ chars, mixed case, numbers, symbols