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
Add field ExpressionEvaluationOptions to set expression evaluation scope while using nested template for azurerm_resource_group_template_deployment
#9723
Closed
neil-yechenwei opened this issue
Dec 7, 2020
· 2 comments
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
Currently, when using a nested template, azurerm_resource_group_template_deployment cannot specify whether template expressions are evaluated within the scope of the parent template or the nested template. So we have to add this new property ExpressionEvaluationOptions to support this scenario.
The "ExpressionEvaluationOptions" property isn't in use. After confirmed with service team, we have to set ""expressionEvaluationOptions": { "scope": "inner" }," in template content to enable ExpressionEvaluationOptions. So we don't need to implement the "ExpressionEvaluationOptions" property.
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
Mar 5, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Description
Currently, when using a nested template,
azurerm_resource_group_template_deployment
cannot specify whether template expressions are evaluated within the scope of the parent template or the nested template. So we have to add this new propertyExpressionEvaluationOptions
to support this scenario.New or Affected Resource(s)
Potential Terraform Configuration
References
The property link: https://github.com/Azure/azure-sdk-for-go/blob/c760106e3c564f57cd7d264c872bc5ef324c592f/services/resources/mgmt/2020-06-01/resources/models.go#L727
The text was updated successfully, but these errors were encountered: