-
Notifications
You must be signed in to change notification settings - Fork 429
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
Move users/databases to for_each #100
Move users/databases to for_each #100
Conversation
Signed-off-by: Dev <devan2patel@gmail.com>
Signed-off-by: Dev <devan2patel@gmail.com>
Signed-off-by: Dev <devan@ingresso.co.uk>
Signed-off-by: Dev <devan@ingresso.co.uk>
Overall LGTM |
The replica configuration blocks are done via resource "google_sql_database_instance" "replicas" {
count = var.read_replica_size |
I think for now lets ignore read replicas, imo that entire section could be more flexible e.g. different instance tiers/settings for different replicas so if/whenever that changes we could move to for_each then as well. |
Do we have any ETA on this? |
Signed-off-by: Dev <devan@ingresso.co.uk>
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.
Thank you and sorry for the delay.
^
Closes #96
Noticed a couple of object fields
instance
andproject
were never used so also removed themTo consider
users
andadditonal_users
+ same for databases, seems a bit pointless having them seperate and since we've already done a breaking API change might as well merge them now.for_each