-
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
TLS_JA3_FINGERPRINT is not supported in google_compute_security_policy resource #17469
TLS_JA3_FINGERPRINT is not supported in google_compute_security_policy resource #17469
Comments
Note from triage: If this field changes frequently, it may be worth removing the enum validation so that the provider doesn't need to be updated when new values are added. |
a workaround is to add a custom header to the backend and rate limit off the that |
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. |
Community Note
Description
[NOT A CONTRIBUTION]
It seems both of version of the provider - "stable" and "beta", don't support setting TLS_JA3_FINGERPRINT in google_compute_security_policy resource, while the documentation [1] and examples [2] show it's possible.
terraform-provider-google/google/services/compute/resource_compute_security_policy.go
Line 221 in ef4977a
New or Affected Resource(s)
Potential Terraform Configuration
References
Docs:
[1] https://cloud.google.com/armor/docs/rate-limiting-overview#identifying_clients_for_rate_limiting
[2] https://cloud.google.com/armor/docs/configure-rate-limiting#ja3
b/328077803
The text was updated successfully, but these errors were encountered: