fix: adjust logic to address manage_master_user_password variable bugs
#131
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.
what and why
manage_master_user_passwordvariable was introduced. The first bug caused a Terraform error where themaster_passwordoutput attempted to join anullvalue when AWS was managing the password, failing with "Invalid function argument: cannot concatenate null values."manage_master_user_password = null(default), random passwords are created and stored in SSM as expected, and whenmanage_master_user_password = true, AWS manages the password without attempting to expose it in Terraform outputs or store it in SSM, maintaining both backward compatibility and the intended securitybug
references