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

docs: azurerm_subnet, the service_endpoints option has additional possible values #2144

Closed
mlcooper opened this issue Oct 23, 2018 · 1 comment · Fixed by #2185
Closed

docs: azurerm_subnet, the service_endpoints option has additional possible values #2144

mlcooper opened this issue Oct 23, 2018 · 1 comment · Fixed by #2185

Comments

@mlcooper
Copy link

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 Version

Terraform v0.11.7
+ provider.azurerm v1.12.0

Affected Resource(s)

  • azurerm_subnet

The service_endpoints option in the documentation, here, has more possible values than the two which are currently listed (Microsoft.Storage, Microsoft.Sql). I believe the possible values now include:
image

I successfully applied Microsoft.AzureActiveDirectory

  • #0000
@tombuildsstuff tombuildsstuff added this to the 1.18.0 milestone Oct 27, 2018
tombuildsstuff added a commit that referenced this issue Oct 30, 2018
…es` (#2185)

* azurerm_subnet: listing all the possible subnet endpoints

Fixes #2144

* Availability Zones are now out of preview

* vm: Availability Set ID now conflicts with Zones

* Fixing the linting
@ghost
Copy link

ghost commented Mar 6, 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 👉 hashibot-feedback@hashicorp.com. Thanks!

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