Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Correct usage of password and allow restored snapshots to set password, username, etc. #384

Merged

Conversation

bryantbiggs
Copy link
Member

@bryantbiggs bryantbiggs commented Feb 18, 2022

Description

  • Correct usage of password - there were some dangling references to master_password that have mostly been resolved (the random password generator name is left as is to avoid any disruptions for users of 4.x)
  • Remove conditional check for snapshot identifier and allow users to set password, username, engine, etc.

Motivation and Context

Breaking Changes

  • No

How Has This Been Tested?

  • I have tested and validated these changes using one or more of the provided examples/* projects
    • Terraform plans only

Copy link

@Spritekin Spritekin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, the username and password management shouldn't be related to the origin of the DB from a snapshot.

@antonbabenko antonbabenko merged commit 81db512 into terraform-aws-modules:master Feb 18, 2022
antonbabenko pushed a commit that referenced this pull request Feb 18, 2022
### [4.1.2](v4.1.1...v4.1.2) (2022-02-18)

### Bug Fixes

* Correct usage of `password` and allow restored snapshots to set password, username, etc. ([#384](#384)) ([81db512](81db512))
@antonbabenko
Copy link
Member

This PR is included in version 4.1.2 🎉

@antonbabenko
Copy link
Member

After the merge, I immediately realized that it should have been feat and minor release (at least) because the output was deleted/renamed.

@bryantbiggs bryantbiggs deleted the fix/upgrade-docs branch February 18, 2022 17:21
@austin-engle
Copy link

How do we properly grab the master password now that the parameter has been removed?

@bryantbiggs
Copy link
Member Author

How do we properly grab the master password now that the parameter has been removed?

with db_instance_password:

output "db_instance_password" {

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Module upgrade tries to empty the password of existing DB
4 participants