Skip to content
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

CIDR validation too strict for azurerm_cosmosdb_account.ip_range_filter #27193

Closed
1 task done
AndreiBarbuOz opened this issue Aug 26, 2024 · 1 comment · Fixed by #27208
Closed
1 task done

CIDR validation too strict for azurerm_cosmosdb_account.ip_range_filter #27193

AndreiBarbuOz opened this issue Aug 26, 2024 · 1 comment · Fixed by #27208

Comments

@AndreiBarbuOz
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Terraform Version

1.9.5

AzureRM Provider Version

4.0.1

Affected Resource(s)/Data Source(s)

azurerm_cosmosdb_account

Terraform Configuration Files

resource "azurerm_cosmosdb_account" "hello_world" {
  name                = var.cosmosdb_account_name
  location            = var.location
  resource_group_name = var.resource_group_name
  offer_type          = "Standard"
  kind                = "GlobalDocumentDB"
  capabilities {
    name = "EnableServerless"
  }

  consistency_policy {
    consistency_level = "Session"
  }

  geo_location {
    location          = var.location
    failover_priority = 0
  }

  public_network_access_enabled = true
  ip_range_filter               = ["0.0.0.0"]
}


### Debug Output/Panic Output

```shell
N/A

Expected Behaviour

According to the Azure documentation, adding 0.0.0.0 to the filter should enable incoming connections from Azure datacenters

See docs: https://learn.microsoft.com/en-us/azure/cosmos-db/how-to-configure-firewall#allow-requests-from-global-azure-datacenters-or-other-sources-within-azure

Actual Behaviour

│ Error: expected "ip_range_filter.0" to be a valid CIDR Value, got 0.0.0.0: invalid CIDR address: 0.0.0.0
│
│   with azurerm_cosmosdb_account.hello_world,
│   on main.tf line 338, in resource "azurerm_cosmosdb_account" "hello_world":
│  338:   ip_range_filter               = ["0.0.0.0"]
│

Steps to Reproduce

No response

Important Factoids

No response

References

No response

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants