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

IoT Hub IP Filter Rules #1699

Closed
jgardner04 opened this issue Aug 1, 2018 · 1 comment · Fixed by #3173
Closed

IoT Hub IP Filter Rules #1699

jgardner04 opened this issue Aug 1, 2018 · 1 comment · Fixed by #3173

Comments

@jgardner04
Copy link
Contributor

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

Description

Add the ability to add IP Filters to the IoT Hub resource. I don't know if this is a new resource or a modification of the current azurerm_iothub resource. This would be completed through the Azure-CLI through something like:

az iot hub update --name test --add properties.ipFilterRules filter_name=test-rule action=Accept ip_mask=10.0.0.0/31

New or Affected Resource(s)

  • azurerm_iothub

Potential Terraform Configuration

resource "azurerm_iothub" "test" {
  name                = "test"
  resource_group_name = "${azurerm_resource_group.test.name}"
  location            = "${azurerm_resource_group.test.location}"
  sku {
    name = "S1"
    tier = "Standard"
    capacity = "1"
  }
  ip_filter {
    name = "ip filter name"
    action = "Accept"
    range = "10.0.0.0/31
  }

  tags {
    "purpose" = "testing"
  }
}

References

@jgardner04 jgardner04 changed the title IoT Hub Filter Rules IoT Hub IP Filter Rules Aug 1, 2018
@ghost
Copy link

ghost commented May 8, 2019

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!

@ghost ghost locked and limited conversation to collaborators May 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants