Skip to content

Conversation

@renato-rudnicki
Copy link
Owner

No description provided.

Copy link
Collaborator

@romanini-ciandt romanini-ciandt left a comment

Choose a reason for hiding this comment

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

To be honest, I didn't understand exactly which is the change implemented here.
Is it ok for us to make a quick review call, so I can make some more questions?

parent_resource_id = local.parent_folder != "" ? local.parent_folder : local.org_id
parent_resource_type = local.parent_folder != "" ? "folder" : "organization"
#parent_resource_id = local.parent_folder != "" ? local.parent_folder : local.org_id
parent_resource_id = local.parent_folder != "" ? local.parent_folder : local.billing_account != "" ? local.billing_account : local.org_id
Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm not sure if I got the intention of this expression right...

You're saying that terraform should use:

  • local.parent_folder if provided;
  • if not, check for local.billing_account and use it if provided;
  • if not, use local.org_id.

But as far as I understood from your reports in our standups, shouldn't the billing account logs sinks in parallel of organization logs, and not instead of organization logs?

# Log Bucket Service account IAM membership billing account #
#-----------------------------------------------------------#

resource "google_project_iam_member" "billing_account_member_logbucket" {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Since this 3 google_project_iam_member resources are granting the same role, with same dependencies for different identities, how about make a for_each iterating by the logbucket, storage and pubsub writer_identity?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants