Resource 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
| Resource() |
Initializes a new instance of the Resource class. |
| Resource(String, String, String, String, IDictionary<String,String>, String, String) |
Initializes a new instance of the Resource class. |
Resource()
Initializes a new instance of the Resource class.
public Resource ();Public Sub New ()Applies to
Resource(String, String, String, String, IDictionary<String,String>, String, String)
Initializes a new instance of the Resource class.
public Resource (string location, string id = default, string name = default, string type = default, System.Collections.Generic.IDictionary<string,string> tags = default, string kind = default, string etag = default);new Microsoft.Azure.Management.Monitor.Models.Resource : string * string * string * string * System.Collections.Generic.IDictionary<string, string> * string * string -> Microsoft.Azure.Management.Monitor.Models.ResourcePublic Sub New (location As String, Optional id As String = Nothing, Optional name As String = Nothing, Optional type As String = Nothing, Optional tags As IDictionary(Of String, String) = Nothing, Optional kind As String = Nothing, Optional etag As String = Nothing)Parameters
- location
- String
Resource location
- id
- String
Azure resource Id
- name
- String
Azure resource name
- type
- String
Azure resource type
- tags
- IDictionary<String,String>
Resource tags
- kind
- String
Metadata used by portal/tooling/etc to render different UX experiences for resources of the same type; e.g. ApiApps are a kind of Microsoft.Web/sites type. If supported, the resource provider must validate and persist this value.
- etag
- String
The etag field is not required. If it is provided in the response body, it must also be provided as a header per the normal etag convention. Entity tags are used for comparing two or more entities from the same requested resource. HTTP/1.1 uses entity tags in the etag (section 14.19), If-Match (section 14.24), If-None-Match (section 14.26), and If-Range (section 14.27) header fields.
