-
Notifications
You must be signed in to change notification settings - Fork 0
sink for billing account #128
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
base: test-pr
Are you sure you want to change the base?
Conversation
romanini-ciandt
left a comment
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.
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?
1-org/envs/shared/log_sinks.tf
Outdated
| 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 |
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'm not sure if I got the intention of this expression right...
You're saying that terraform should use:
local.parent_folderif provided;- if not, check for
local.billing_accountand 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" { |
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.
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?
No description provided.