-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Max utilization is not supported for Serverless network endpoint groups. #7051
Max utilization is not supported for Serverless network endpoint groups. #7051
Comments
Ah yeah, I made this work specifically for global NEGs based on inferring type from their URL. A similar check will be needed for regional NEGs |
I attempted setting max_utilization (which is documented as being optional) to null (from its default value of 0.8), but to no avail. |
This is still happening in 3.36 @slevenick |
@icco it looks like this was merged just after the 3.36 release was cut. It will be in the 3.37 release expected next monday |
Is there any way I can test it or use it before then? I ask because we have a big release next week, and if there are bugs I'd love to not wait another week. |
Yes! You can build the provider from source and use it locally. Directions are here: https://github.com/hashicorp/terraform-provider-google#building-the-provider |
Small note on this: while it works, the maxUtilization etc values are still shown in the terraform plan output. |
Yeah, that's due to maxUtilization having a default value. It's tricky to remove without causing a breaking change, so I went with leaving it in the plan but stripping it from the request for serverless NEGs |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
Affected Resource(s)
Terraform Configuration Files
This is a simplified config that triggers the bug. A full example can be found at google/exposure-notifications-verification-server#248
Debug Output
https://gist.github.com/icco/0e29297c1cb2e8e47b9c0759c1f84c87
Panic Output
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
With the new serverless endpoint type, the default values we send are no longer valid.
References
The text was updated successfully, but these errors were encountered: