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 subscription scoped deployments in azurerm_template_deployment #6561

Closed
landro opened this issue Apr 21, 2020 · 5 comments · Fixed by #8672
Closed

Support for subscription scoped deployments in azurerm_template_deployment #6561

landro opened this issue Apr 21, 2020 · 5 comments · Fixed by #8672

Comments

@landro
Copy link

landro commented Apr 21, 2020

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 azurerm_template_deployment requires a resource group name.
Arm templates are not necessary deployed at the resource group level, but also at the subscription level:

budgets
deployments - for nested templates that deploy to resource groups.
eventSubscriptions
peerAsns
policyAssignments
policyDefinitions
policySetDefinitions
remediations
resourceGroups
roleAssignments
roleDefinitions
scopeAssignments
supportPlanTypes
tags

Support for this should be added.

New or Affected Resource(s)

  • azurerm_template_deployment

References

@pearcec
Copy link
Contributor

pearcec commented Apr 23, 2020

It looks like there are a few other options as well, such as tenant level, managed group. I would want to check with the maintainers on direction. My initial thoughts are to have a separate resource type since the SDK and Azure has a different REST API. Right now the azurerm_tempalte_deployment requires resource_group_name which would be tricky to change to optional.

@kellmv1

This comment has been minimized.

@vinodkengg

This comment has been minimized.

@ghost
Copy link

ghost commented Oct 1, 2020

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

@ghost
Copy link

ghost commented Nov 1, 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 as resolved and limited conversation to collaborators Nov 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.