TemplateLink Constructors
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Overloads
TemplateLink() |
Initializes a new instance of the TemplateLink class. |
TemplateLink(String, String, String, String, String) |
Initializes a new instance of the TemplateLink class. |
TemplateLink()
Initializes a new instance of the TemplateLink class.
public TemplateLink ();
Public Sub New ()
Applies to
TemplateLink(String, String, String, String, String)
Initializes a new instance of the TemplateLink class.
public TemplateLink (string uri = default, string id = default, string relativePath = default, string contentVersion = default, string queryString = default);
new Microsoft.Azure.Management.ResourceManager.Fluent.Models.TemplateLink : string * string * string * string * string -> Microsoft.Azure.Management.ResourceManager.Fluent.Models.TemplateLink
Public Sub New (Optional uri As String = Nothing, Optional id As String = Nothing, Optional relativePath As String = Nothing, Optional contentVersion As String = Nothing, Optional queryString As String = Nothing)
Parameters
- uri
- String
The URI of the template to deploy. Use either the uri or id property, but not both.
- id
- String
The resource id of a Template Spec. Use either the id or uri property, but not both.
- relativePath
- String
The relativePath property can be used to deploy a linked template at a location relative to the parent. If the parent template was linked with a TemplateSpec, this will reference an artifact in the TemplateSpec. If the parent was linked with a URI, the child deployment will be a combination of the parent and relativePath URIs
- contentVersion
- String
If included, must match the ContentVersion in the template.
- queryString
- String
The query string (for example, a SAS token) to be used with the templateLink URI.
Applies to
意見反應
https://aka.ms/ContentUserFeedback。
即將登場:在 2024 年,我們將逐步淘汰 GitHub 問題作為內容的意見反應機制,並將它取代為新的意見反應系統。 如需詳細資訊,請參閱:提交並檢視相關的意見反應