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.
Thanks for the answer.
It seems that the current abillity of terraform is to support a SLO goal of up to 0.999 but not 0.9999. goal - (Required) The fraction of service that must be good in order for this objective to be met. 0 < goal <= 0.999 Link.
Google recently updated it from 0.999 to 0.9999, as can be seen in the link I provided: The fraction of service that must be good in order for this objective to be met. 0 < goal <= 0.9999.
If terraform does support a 0.9999 goal, can you please share a link to the release notes?
@AmirBagaon according to the documentation on terraform registry it is what it is. On the other hand, if you have any official Google source that indicates otherwise, please share it to verify the topic.
Community Note
Terraform Version & Provider Version(s)
Terraform v0.14.6
on linux amd64
Affected Resource(s)
google_monitoring_slo
Terraform Configuration
Debug Output
No response
Expected Behavior
Recently Google updated their SLO goal to be in range of 0 < goal <= 0.9999.
Link.
Actual Behavior
Error: goal 0.999900 must be > 0 and <= 0.999
Steps to reproduce
terraform apply
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: