-
Notifications
You must be signed in to change notification settings - Fork 170
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
Update google CFT module "terraform-google-bigquery" #350
Comments
Hi Team, Please release new version which will support minimum google provider version as v5.42.0 (current provider version is version = ">= 5.3, < 7"). When adding same IAM role using CFT module input block "access" and "google_bigquery_dataset_iam_member" resource type, we are facing some conflict, authorize views added to dataset is getting removed. This issue is solved in google provider version as v5.42.0. Hence we would request you to update module terraform-google-bigquery minimum provider version to v5.42.0. |
Hi our constraint of
|
Hi Team, We tried running the terraform plan & apply using google provider version v5.42 and above version. We are seeing IAM roles added using "access" and "google_bigquery_dataset_iam_member" blocks are still conflicting , roles are removing in first build and getting added in next build. This is continuing in every build. please see the below terraform code and terraform plan for your reference. #main.tf file resource "google_bigquery_dataset_iam_member" "newtestdemo_member_sa_1" { resource "google_bigquery_dataset_iam_member" "newtestdemo_member_sa_2" { resource "google_bigquery_dataset_iam_member" "newtestdemo_member_user_1" { resource "google_bigquery_dataset_iam_member" "newtestdemo_member_group_1" { #variable file variable "psvalues1" { #tfvar file
} Terraform plan first timemodule.bigquery["testdemo"].google_bigquery_dataset.main will be updated in-place~ resource "google_bigquery_dataset" "main" {
################################ Terraform plan second timeTerraform will perform the following actions: google_bigquery_dataset_iam_member.newtestdemo_member_group_1 will be created
google_bigquery_dataset_iam_member.newtestdemo_member_sa_1 will be created
google_bigquery_dataset_iam_member.newtestdemo_member_sa_2 will be created
google_bigquery_dataset_iam_member.newtestdemo_member_user_1 will be created
|
TL;DR
Latest google provider version "v5.42.0" made resource type "google_bigquery_dataset_iam_member" non-authoritative which fixes the conflict with "google_bigquery_dataset_access" resource type. When adding member for same IAM role using "google_bigquery_dataset_iam_member" and "google_bigquery_dataset_access" resource type used to remove authorize views added in the dataset.
Can you please help us bring this changes to google CFT module "terraform-google-bigquery" so we don't face the above issue when adding IAM role using CFT module input block "access" and "google_bigquery_dataset_iam_member" resource type.
Terraform Resources
https://registry.terraform.io/modules/terraform-google-modules/bigquery/google/latest
Detailed design
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: