-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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_cosmosdb_account ip_range_filter doesn't actually allow /8 in CIDR #18134
Comments
I'm being blocked by this bug as well. Trying to use: terraform-provider-azurerm/internal/services/cosmos/cosmosdb_account_resource.go Line 272 in 00e020c
to: regexp.MustCompile(`^(\b(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)(/([1-2]?[0-9]|3[0-2]))?\b[,]?)*$`), Would you accept a PR? |
We're blocked by this as well |
Same thing for me. I added private endpoints to our instances, which immediately blocked public access. The only way to handle that is to add the following list of IP ranges: @bart-vmware I'd suggest replacing the current RegEx with |
Added PR for the issue #24306 |
Is there an existing issue for this?
Community Note
Terraform Version
v1.2.8
AzureRM Provider Version
v3.20.0
Affected Resource(s)/Data Source(s)
azurerm_cosmosdb_account
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
to create the cluster with the filter requested
Actual Behaviour
the error
notes
Steps to Reproduce
you need to have an existing whatever-group-name
Important Factoids
No response
References
This reference is only provided as support for the statement "azure does not accept private ip ranges there"
#7946
The text was updated successfully, but these errors were encountered: