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

Azurerm_search_service should allow CIDR blocks in the allowed_ips section #9488

Closed
tpyle opened this issue Nov 25, 2020 · 3 comments · Fixed by #9493
Closed

Azurerm_search_service should allow CIDR blocks in the allowed_ips section #9488

tpyle opened this issue Nov 25, 2020 · 3 comments · Fixed by #9493

Comments

@tpyle
Copy link

tpyle commented Nov 25, 2020

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 "+1" or "me too" comments, 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

Terraform (and AzureRM Provider) Version

terraform v0.13.4
azurerm v2.37.0

Affected Resource(s)

  • azurerm_search_service

Terraform Configuration Files

resource "azurerm_search_service" "ss" {
    name = "example-search-service"
    resource_group_name = "example-rg"
    location = "westus2"
    sku = "basic"
    public_network_access_enabled = false
    allowed_ips = ["1.2.3.0/24", "2.3.0.0/16"]
}

Debug Output

N/A

Panic Output

N/A

Expected Behaviour

The resource should have been created successfully, as per the documentation and the portal, which indicate that CIDR blocks are allowed in the network rules

Actual Behaviour

The provider throws an error that the CIDR block is an invalid IP address:
Error: "allowed_ips.0" is not a valid IPv4 address

Steps to Reproduce

  1. terraform apply or terraform plan

Important Factoids

References

  • #0000
@neil-yechenwei
Copy link
Contributor

Thanks for opening this issue. Hopes the fix would be helpful.

@ghost
Copy link

ghost commented Nov 27, 2020

This has been released in version 2.38.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.38.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Dec 26, 2020

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 ghost locked as resolved and limited conversation to collaborators Dec 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants