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
When I use a duration in a condition block in a librato_alert, the duration is not set during the creation of the alert. A subsequent terraform apply attempts to set the duration, but this also fails due to #8966.
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 22, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When I use a
duration
in acondition
block in alibrato_alert
, the duration is not set during the creation of the alert. A subsequentterraform apply
attempts to set the duration, but this also fails due to #8966.Terraform Version
0.7.4
Affected Resource(s)
librato_alert
Terraform Configuration Files
Debug Output
https://gist.github.com/jonleighton/b82e81e6ba92ffb80b5418cf247cce58
Expected Behavior
The alert's condition should have been created with a duration.
Actual Behavior
The alert's condition was created to trigger immediately.
Steps to Reproduce
curl -u '<email>:<token>' -d 'gauges[0][name]=test' -d 'gauges[0][value]=60' -X POST https://metrics-api.librato.com/v1/metrics
to create a metricterraform apply -var 'librato_email=<email>' -var 'librato_token=<token>'
Now observe in Librato Metrics that the alert condition doesn't have the duration specified.
A subsequent
terraform apply
will detect this, and try to modify the alert. However this will also fail, due to #8966.References
The text was updated successfully, but these errors were encountered: