You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If an issue is assigned to a user, that user is claiming responsibility for the issue.
Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.
We should be able to set disable_default_iam_recipients as true in all cases.
Actual Behavior
If I mark disable_default_iam_recipients as true, when the monitoring_notification_channels are not set (only pubsub), or when threshold_rules are set (which is normal), we get that generic "Request contains an invalid argument" error.
Steps to reproduce
terraform apply
Important Factoids
No response
References
No response
b/335295571
The text was updated successfully, but these errors were encountered:
Community Note
Terraform Version
1.6.3
Affected Resource(s)
google_billing_budget
Terraform Configuration
Debug Output
Error updating Budget "billingAccounts/123/budgets/12345": googleapi: Error 400: Request contains an invalid argument.
Expected Behavior
We should be able to set disable_default_iam_recipients as true in all cases.
Actual Behavior
If I mark disable_default_iam_recipients as true, when the monitoring_notification_channels are not set (only pubsub), or when threshold_rules are set (which is normal), we get that generic "Request contains an invalid argument" error.
Steps to reproduce
terraform apply
Important Factoids
No response
References
No response
b/335295571
The text was updated successfully, but these errors were encountered: