-
Notifications
You must be signed in to change notification settings - Fork 4.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
azurerm_eventhub_consumer_group doesn't support '$Default' consumer group name #7720
Comments
This comment has been minimized.
This comment has been minimized.
It is a default consumer group, you don't need to create it, moreover, you can't manage it in any way. |
For clarity - The Resource cannot create or otherwise manage |
This has been released in version 2.28.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 2.28.0"
}
# ... other configuration ... |
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 👉 [email protected]. Thanks! |
Community Note
Terraform (and AzureRM Provider) Version
Affected Resource(s)
azurerm_eventhub_consumer_group
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Should have accepted the name
$Default
as this is the name that the azure portal assigns by default if one is not specified, when using theBasic
Tier Event Hub Namespace.Actual Behavior
Error: invalid value for name (The consumer group name can contain only letters, numbers, periods (.), hyphens (-),and underscores (_), up to 50 characters, and it must begin and end with a letter or number.)
Steps to Reproduce
As per example above
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: