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

Relax naming requirements of app_service_plan #1336

Closed
phekmat opened this issue Jun 1, 2018 · 2 comments · Fixed by #1351
Closed

Relax naming requirements of app_service_plan #1336

phekmat opened this issue Jun 1, 2018 · 2 comments · Fixed by #1351

Comments

@phekmat
Copy link
Contributor

phekmat commented Jun 1, 2018

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

azurerm_app_service_plan uses a more strict naming convention than the API (notably, _ is not allowed in terraform, but is via the API and ARM templates). We have app service plans with an _ in the name, so this is a blocker when it comes to using this resource.

New or Affected Resource(s)

  • azurerm_app_service_plan
@katbyte
Copy link
Collaborator

katbyte commented Jun 16, 2018

Hey @phekmat,

1.7 that was released today and it should allow for underscores in the azurerm_app_service_plan name.

@ghost
Copy link

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