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

There is no support for vnet_subnet_id in azurerm_api_management? #4942

Closed
ghost opened this issue Nov 21, 2019 · 2 comments
Closed

There is no support for vnet_subnet_id in azurerm_api_management? #4942

ghost opened this issue Nov 21, 2019 · 2 comments

Comments

@ghost
Copy link

ghost commented Nov 21, 2019

Hello together,

I read many issues about azurerm_api_management support for subnet reference in the azurerm_api_management resource. But it looks like it's not implemented yet?

resource "azurerm_api_management" "api_gateway"{
...
  vnet_subnet_id = "subnetXY"
  vnet_type = "External"
...
}

Like here
and here

Well, still after that time there is no solution in sight? Do we must workaround with an arm template in terraform...

I really appreciate any suggestions since I lost already one day.

https://www.terraform.io/docs/providers/azurerm/r/api_management.html

@tombuildsstuff
Copy link
Member

hi @Anonymous202020

Thanks for opening this issue.

This functionality isn't supported at this time due to a bug in the Azure API - the upstream issue tracking this is here but essentially when the new API version goes live (and is available in the Azure SDK for Go), it should be possible to upgrade to this and for someone to take a look into the API Management issues that are blocked by this (example).

Unfortunately in the interim there's not a whole bunch we can do to work around this - support for this is being tracked in #3667, and rather than having multiple issues open tracking the same thing I'm going to close this in favour of #3667 - would you mind subscribing to that issue for updates?

Thanks!

@ghost
Copy link

ghost commented Mar 29, 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 and limited conversation to collaborators Mar 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant