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

Need to explain ContentVersion #9402

Closed
jtuliani opened this issue May 30, 2018 — with docs.microsoft.com · 3 comments
Closed

Need to explain ContentVersion #9402

jtuliani opened this issue May 30, 2018 — with docs.microsoft.com · 3 comments

Comments

Copy link

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.

@femsulu
Copy link
Member

femsulu commented May 30, 2018

@jtuliani, Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

@tfitzmac
Copy link
Contributor

@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.

@djberg96
Copy link

djberg96 commented Oct 1, 2018

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants