-
Notifications
You must be signed in to change notification settings - Fork 428
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!: pass iam_user_emails as map to postgres module #414
fix!: pass iam_user_emails as map to postgres module #414
Conversation
76e90b2
to
f95a008
Compare
@mnahkies |
Thanks for catching this @mnahkies. Can you make
|
this solves the "Error: Invalid for_each argument" issue that occurs if you try to create a service account and database in the same root module. (it's a bit awkward but to my knowledge this is the correct way to do it in `terraform`) fixes issue terraform-google-modules#413
3ab6184
to
5f582c9
Compare
|
||
``` | ||
|
||
We recommend using `moved` blocks as [documented here](https://developer.hashicorp.com/terraform/language/modules/develop/refactoring) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I saw that the minimum supported terraform version is now 1.3.0
since v14
and so I think we should encourage the use of moved
blocks over running terraform state mv
commands, but let me know if you disagree
Apologies that it's taken me so long to get back to this @g-awmalik - I was bogged down with life stuff for a few weeks. I've now:
If you could please take another look that would be great :) |
Co-authored-by: Kareem Daggash <kareemdaggash@gmail.com>
@g-awmalik any chance you would have time to give this a re-review / approve a CI run? |
/gcbrun |
/gcbrun |
/gcbrun |
this solves the
Error: Invalid for_each argument
issue that occurs if you try to create a service account and database in the same root module.(it's a bit awkward but to my knowledge this is the correct way to do it in
terraform
)fixes issue #413
Notes
Obviously this is a breaking change - I expect we'll want to add migration instructions to https://github.com/mnahkies/terraform-google-sql-db/blob/7d6b2095f0e2312424c97a416dbb929d57c73eaa/docs/upgrading_to_sql_db_14.0.0.md or the v15 equivalent - ideally I'd like some feedback on whether this change will be accepted before producing these though.
I think it would be nice to get this into the v14 release, given that it already contains other IAM related breaking changes to the
postgres
module.