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

Support for IpsecTrafficSelectorPolicy #6272

Closed
carloVentrella opened this issue Mar 26, 2020 · 2 comments · Fixed by #6586
Closed

Support for IpsecTrafficSelectorPolicy #6272

carloVentrella opened this issue Mar 26, 2020 · 2 comments · Fixed by #6586

Comments

@carloVentrella
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

Right now I haven't found a way to defined traffic selector policy while creating an ipsec connection.
This is indeed feasible with power shell:

https://docs.microsoft.com/en-us/powershell/module/az.network/new-azipsectrafficselectorpolicy?view=azps-3.6.1

It would be nice to integrate it in the connection resource.

New or Affected Resource(s)

  • azurerm_virtual_network_gateway_connection

Potential Terraform Configuration

resource "azurerm_virtual_network_gateway_connection" "conn" {

    use_policy_based_traffic_selectors = true

    traffic_selector_policy {
        local_address_range = "10.0.0.0/24"
        remote_address_range = "40.40.40.0/24"
    }

}
@ghost
Copy link

ghost commented Jul 16, 2020

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

@ghost
Copy link

ghost commented Aug 13, 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 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Aug 13, 2020
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.

3 participants