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
azurerm_servicebus_subscription.sub_orderManagementPublisher: invalid value for topic_name (The topic name can contain only letters, numbers, periods, hyphens and underscores. The namespace must start with a letter, and it must end with a letter or number and be less then 260 characters long.)
Expected Behavior
The subscription to the topic should have been created
Actual Behavior
The creation of the subscription failed since the topic has ~ in the name
Steps to Reproduce
simply plan or apply the configuration
Important Factoids
Using version 1.9.0 of the azurerm provider doesn't exhibit this behaviour
I am still able to provision the topic with ~ in the name using azurerm_servicebus_topic
References
#0000
The text was updated successfully, but these errors were encountered:
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
Community Note
Terraform Version
Terraform v0.11.7
Affected Resource(s)
azurerm_servicebus_subscription
Terraform Configuration Files
Debug Output
Panic Output
Error: Error running plan: 1 error(s) occurred:
Expected Behavior
The subscription to the topic should have been created
Actual Behavior
The creation of the subscription failed since the topic has ~ in the name
Steps to Reproduce
Important Factoids
Using version 1.9.0 of the azurerm provider doesn't exhibit this behaviour
I am still able to provision the topic with ~ in the name using azurerm_servicebus_topic
References
The text was updated successfully, but these errors were encountered: