You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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
locked as resolved and limited conversation to collaborators
Nov 1, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
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:
Support for this should be added.
New or Affected Resource(s)
References
The text was updated successfully, but these errors were encountered: