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

resource/aws_db_instance: Force update when snapshot_identifier is set #2869

Closed

Conversation

atsushi-ishibashi
Copy link
Contributor

@atsushi-ishibashi atsushi-ishibashi commented Jan 5, 2018

Closes #2859

If there is a reason why update was executed only when password, vpc_security_group_ids, security_group_names were set, please correct me🙇

@Ninir Ninir added the bug Addresses a defect in current functionality. label Jan 5, 2018
@bflad bflad added the service/rds Issues and PRs that pertain to the rds service. label Jan 11, 2018
@radeksimko radeksimko changed the title r/db_instance: Force update when snapshot_identifier is set resource/aws_db_instance: Force update when snapshot_identifier is set Jan 16, 2018
Copy link
Member

@radeksimko radeksimko left a comment

Choose a reason for hiding this comment

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

Thanks for the PR, as usually @atsushi-ishibashi

Do you mind attaching an acceptance test with a config that can exercise this new patch?

@radeksimko radeksimko added the waiting-response Maintainers are waiting on response from community or contributor. label Feb 16, 2018
@atsushi-ishibashi
Copy link
Contributor Author

@radeksimko Do you have any ideas of an acceptance test for snapshot?
I'm thinking that I make 2 test steps, the first creating db_instance with specifying final_snapshot_identifier and the second restoring db_instance with the snapshot_identifier.
How do you think?

@bflad bflad removed the waiting-response Maintainers are waiting on response from community or contributor. label May 31, 2018
@bflad bflad closed this in #5621 Aug 22, 2018
@ghost
Copy link

ghost commented Apr 3, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/rds Issues and PRs that pertain to the rds service.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

aws_db_instance parameter_group_name Ignored
4 participants