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
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!
ghost
locked and limited conversation to collaborators
Mar 30, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
(Incidentally I got the
PT1H
value from setting TTL manually in the portal to 1 hour and copying the output from aterraform plan
value afterward)Expected Behavior
default_message_ttl
set to 1 hourActual Behavior
default_message_ttl
set to a ridiculously large number of daysSteps to Reproduce
terraform apply
<snip>
Which looks great. However if I run
terraform apply
again or view the subscription in the portal, it's still set to a ludicrously high value.Important Factoids
Note that I'm setting the same
PT1H
value in a servicebus topic and it's being set correctly to 1 hour.The text was updated successfully, but these errors were encountered: