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 can this article be enhanced to explain content version?
For nested templates, the nested template contains 'contentVersion'. But does it do anything?
For linked templates, the linked template contains 'contentVersion' and the parent template also contains a 'contentVersion' property for the linked template. How are these two related? Does Resource Manager include any logic to ensure the content versions match in any way?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 6ec87df7-43e5-2d11-3546-9f338534e560
Version Independent ID: c5319e4e-7d0c-6c94-b53e-6689f2d041c2
@jtuliani - thanks for this question. I added some content to clarify its usage. Basically, the contentVersion is a required property of a template, so when you use a nested template, you have to include it. When linking to a template, you do not have to specify a content version. But, if you do provide it, it must match the version in the template.
There is no connection between the version in the parent template and linked templates. They can both iterate at different schedules.
@tfitzmac Thanks for this, though I'm confused as to why the contentVersion isn't a displayed property when I do an az group deployment show for deployments that weren't created using external links.
Please can this article be enhanced to explain content version?
For nested templates, the nested template contains 'contentVersion'. But does it do anything?
For linked templates, the linked template contains 'contentVersion' and the parent template also contains a 'contentVersion' property for the linked template. How are these two related? Does Resource Manager include any logic to ensure the content versions match in any way?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: