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

snapshot_identifier default value causing validation conflict in aws provider 3.29 #291

Closed
fractos opened this issue Feb 20, 2021 · 8 comments

Comments

@fractos
Copy link

fractos commented Feb 20, 2021

As of yesterday, aws provider 3.29 now has validation on whether a username and a snapshot identifier are set. This appears to be sensitive to whether null or "" is used. The default in this module is "" which busts the validation.

This is currently being tracked in hashicorp/terraform-provider-aws#17712

By way of mitigation, could we consider changing the default for snapshot_identifier to null ?

@rollue
Copy link

rollue commented Feb 21, 2021

I can confirm this is happening in my development settings too.

@aleon1220
Copy link

is happenning to me now and i am on terraform cloud. I believe the conflict is in
the duplicate use of the var.snapshot_identifier

Take a look at line 63 and 139

https://github.com/terraform-aws-modules/terraform-aws-rds/blob/master/modules/db_instance/main.tf#L139

@aleon1220
Copy link

I think the majority of the community is tracking the issue at hashicorp/terraform-provider-aws#17712

@bryantbiggs
Copy link
Member

hi all - can you re-check now since we have made the change to use null in #289

@evanstachowiak
Copy link

The new version fixed it for me, @bryantbiggs

@bryantbiggs
Copy link
Member

thanks @evanstachowiak - closing this out for now but if there are any other issues, pleas feel free to open a new issue

@fractos
Copy link
Author

fractos commented Mar 1, 2021

@bryantbiggs Yep that's fixed it for us as well. Thanks! Well, in combination with the reversion of the AWS provider change.

@github-actions
Copy link

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 have found a problem that seems similar to this, 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 15, 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

No branches or pull requests

5 participants