@pulumi/vsphere 4.16.2 → 4.16.3

package/getResourcePool.d.ts

@@ -3,7 +3,9 @@ import * as pulumi from "@pulumi/pulumi";
  * The `vsphere.ResourcePool` data source can be used to discover the ID of a
  * resource pool in vSphere. This is useful to return the ID of a resource pool
  * that you want to use to create virtual machines in using the
- * `vsphere.VirtualMachine` resource.
+ * [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource.
+ *
+ * [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
  *
  * ## Example Usage
  *
@@ -43,9 +45,11 @@ import * as pulumi from "@pulumi/pulumi";
  *
  * ### Specifying the Root Resource Pool for a Standalone ESXi Host
  *
- * > **NOTE:** Returning the root resource pool for a cluster can be done
- * directly via the `vsphere.ComputeCluster`
- * data source.
+ * > **NOTE:** Returning the root resource pool for a cluster can be done directly
+ * via the [`vsphere.ComputeCluster`][docs-compute-cluster-data-source] data
+ * source.
+ *
+ * [docs-compute-cluster-data-source]: /docs/providers/vsphere/d/compute_cluster.html
  *
  * All compute resources in vSphere have a resource pool, even if one has not been
  * explicitly created. This resource pool is referred to as the _root resource
@@ -73,11 +77,11 @@ export declare function getResourcePool(args?: GetResourcePoolArgs, opts?: pulum
  */
 export interface GetResourcePoolArgs {
     /**
-     * The managed object reference ID
-     * of the datacenter in which the resource pool is located. This can be omitted
-     * if the search path used in `name` is an absolute path. For default
-     * datacenters, use the id attribute from an empty `vsphere.Datacenter` data
-     * source..
+     * The
+     * [managed object reference ID][docs-about-morefs] of the datacenter in which
+     * the resource pool is located. This can be omitted if the search path used in
+     * `name` is an absolute path. For default datacenters, use the id attribute from
+     * an empty `vsphere.Datacenter` data source.
      */
     datacenterId?: string;
     /**
@@ -86,13 +90,15 @@ export interface GetResourcePoolArgs {
      */
     name?: string;
     /**
-     * The managed object ID
+     * The [managed object ID][docs-about-morefs]
      * of the parent resource pool. When specified, the `name` parameter is used to find
      * a child resource pool with the given name under this parent resource pool.
      *
-     * > **Note:** When using ESXi without a vCenter Server instance, you do not
-     * need to specify either attribute to use this data source. An empty declaration
-     * will load the ESXi host's root resource pool.
+     * [docs-about-morefs]: /docs/providers/vsphere/index.html#use-of-managed-object-references-by-the-vsphere-provider
+     *
+     * > **Note:** When using ESXi without a vCenter Server instance, you do not need
+     * to specify either attribute to use this data source. An empty declaration will
+     * load the ESXi host's root resource pool.
      */
     parentResourcePoolId?: string;
 }
@@ -112,7 +118,9 @@ export interface GetResourcePoolResult {
  * The `vsphere.ResourcePool` data source can be used to discover the ID of a
  * resource pool in vSphere. This is useful to return the ID of a resource pool
  * that you want to use to create virtual machines in using the
- * `vsphere.VirtualMachine` resource.
+ * [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource.
+ *
+ * [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
  *
  * ## Example Usage
  *
@@ -152,9 +160,11 @@ export interface GetResourcePoolResult {
  *
  * ### Specifying the Root Resource Pool for a Standalone ESXi Host
  *
- * > **NOTE:** Returning the root resource pool for a cluster can be done
- * directly via the `vsphere.ComputeCluster`
- * data source.
+ * > **NOTE:** Returning the root resource pool for a cluster can be done directly
+ * via the [`vsphere.ComputeCluster`][docs-compute-cluster-data-source] data
+ * source.
+ *
+ * [docs-compute-cluster-data-source]: /docs/providers/vsphere/d/compute_cluster.html
  *
  * All compute resources in vSphere have a resource pool, even if one has not been
  * explicitly created. This resource pool is referred to as the _root resource
@@ -182,11 +192,11 @@ export declare function getResourcePoolOutput(args?: GetResourcePoolOutputArgs,
  */
 export interface GetResourcePoolOutputArgs {
     /**
-     * The managed object reference ID
-     * of the datacenter in which the resource pool is located. This can be omitted
-     * if the search path used in `name` is an absolute path. For default
-     * datacenters, use the id attribute from an empty `vsphere.Datacenter` data
-     * source..
+     * The
+     * [managed object reference ID][docs-about-morefs] of the datacenter in which
+     * the resource pool is located. This can be omitted if the search path used in
+     * `name` is an absolute path. For default datacenters, use the id attribute from
+     * an empty `vsphere.Datacenter` data source.
      */
     datacenterId?: pulumi.Input<string>;
     /**
@@ -195,13 +205,15 @@ export interface GetResourcePoolOutputArgs {
      */
     name?: pulumi.Input<string>;
     /**
-     * The managed object ID
+     * The [managed object ID][docs-about-morefs]
      * of the parent resource pool. When specified, the `name` parameter is used to find
      * a child resource pool with the given name under this parent resource pool.
      *
-     * > **Note:** When using ESXi without a vCenter Server instance, you do not
-     * need to specify either attribute to use this data source. An empty declaration
-     * will load the ESXi host's root resource pool.
+     * [docs-about-morefs]: /docs/providers/vsphere/index.html#use-of-managed-object-references-by-the-vsphere-provider
+     *
+     * > **Note:** When using ESXi without a vCenter Server instance, you do not need
+     * to specify either attribute to use this data source. An empty declaration will
+     * load the ESXi host's root resource pool.
      */
     parentResourcePoolId?: pulumi.Input<string>;
 }

package/getResourcePool.js

@@ -9,7 +9,9 @@ const utilities = require("./utilities");
  * The `vsphere.ResourcePool` data source can be used to discover the ID of a
  * resource pool in vSphere. This is useful to return the ID of a resource pool
  * that you want to use to create virtual machines in using the
- * `vsphere.VirtualMachine` resource.
+ * [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource.
+ *
+ * [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
  *
  * ## Example Usage
  *
@@ -49,9 +51,11 @@ const utilities = require("./utilities");
  *
  * ### Specifying the Root Resource Pool for a Standalone ESXi Host
  *
- * > **NOTE:** Returning the root resource pool for a cluster can be done
- * directly via the `vsphere.ComputeCluster`
- * data source.
+ * > **NOTE:** Returning the root resource pool for a cluster can be done directly
+ * via the [`vsphere.ComputeCluster`][docs-compute-cluster-data-source] data
+ * source.
+ *
+ * [docs-compute-cluster-data-source]: /docs/providers/vsphere/d/compute_cluster.html
  *
  * All compute resources in vSphere have a resource pool, even if one has not been
  * explicitly created. This resource pool is referred to as the _root resource
@@ -87,7 +91,9 @@ exports.getResourcePool = getResourcePool;
  * The `vsphere.ResourcePool` data source can be used to discover the ID of a
  * resource pool in vSphere. This is useful to return the ID of a resource pool
  * that you want to use to create virtual machines in using the
- * `vsphere.VirtualMachine` resource.
+ * [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource.
+ *
+ * [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
  *
  * ## Example Usage
  *
@@ -127,9 +133,11 @@ exports.getResourcePool = getResourcePool;
  *
  * ### Specifying the Root Resource Pool for a Standalone ESXi Host
  *
- * > **NOTE:** Returning the root resource pool for a cluster can be done
- * directly via the `vsphere.ComputeCluster`
- * data source.
+ * > **NOTE:** Returning the root resource pool for a cluster can be done directly
+ * via the [`vsphere.ComputeCluster`][docs-compute-cluster-data-source] data
+ * source.
+ *
+ * [docs-compute-cluster-data-source]: /docs/providers/vsphere/d/compute_cluster.html
  *
  * All compute resources in vSphere have a resource pool, even if one has not been
  * explicitly created. This resource pool is referred to as the _root resource

package/getResourcePool.js.map

@@ -1 +1 @@
-{"version":3,"file":"getResourcePool.js","sourceRoot":"","sources":["../getResourcePool.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmEG;AACH,SAAgB,eAAe,CAAC,IAA0B,EAAE,IAA2B;IACnF,IAAI,GAAG,IAAI,IAAI,EAAE,CAAC;IAClB,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,+CAA+C,EAAE;QAC1E,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;QACjB,sBAAsB,EAAE,IAAI,CAAC,oBAAoB;KACpD,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AARD,0CAQC;AA2CD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmEG;AACH,SAAgB,qBAAqB,CAAC,IAAgC,EAAE,IAAiC;IACrG,IAAI,GAAG,IAAI,IAAI,EAAE,CAAC;IAClB,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,YAAY,CAAC,+CAA+C,EAAE;QAChF,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;QACjB,sBAAsB,EAAE,IAAI,CAAC,oBAAoB;KACpD,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AARD,sDAQC"}
+{"version":3,"file":"getResourcePool.js","sourceRoot":"","sources":["../getResourcePool.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAuEG;AACH,SAAgB,eAAe,CAAC,IAA0B,EAAE,IAA2B;IACnF,IAAI,GAAG,IAAI,IAAI,EAAE,CAAC;IAClB,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,+CAA+C,EAAE;QAC1E,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;QACjB,sBAAsB,EAAE,IAAI,CAAC,oBAAoB;KACpD,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AARD,0CAQC;AA6CD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAuEG;AACH,SAAgB,qBAAqB,CAAC,IAAgC,EAAE,IAAiC;IACrG,IAAI,GAAG,IAAI,IAAI,EAAE,CAAC;IAClB,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,YAAY,CAAC,+CAA+C,EAAE;QAChF,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;QACjB,sBAAsB,EAAE,IAAI,CAAC,oBAAoB;KACpD,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AARD,sDAQC"}

package/getTag.d.ts

@@ -1,10 +1,12 @@
 import * as pulumi from "@pulumi/pulumi";
 /**
- * The `vsphere.Tag` data source can be used to reference tags that are not
- * managed by this provider. Its attributes are exactly the same as the `vsphere.Tag`
- * resource, and, like importing, the data source takes a name and
- * category to search on. The `id` and other attributes are then populated with
- * the data found by the search.
+ * The `vsphere.Tag` data source can be used to reference tags that are not managed
+ * by Terraform. Its attributes are exactly the same as the
+ * [`vsphere.Tag` resource][resource-tag], and, like importing, the data source
+ * uses a name and category as search criteria. The `id` and other attributes are
+ * populated with the data found by the search.
+ *
+ * [resource-tag]: /docs/providers/vsphere/r/tag.html
  *
  * > **NOTE:** Tagging is not supported on direct ESXi hosts connections and
  * requires vCenter Server.
@@ -52,11 +54,13 @@ export interface GetTagResult {
     readonly name: string;
 }
 /**
- * The `vsphere.Tag` data source can be used to reference tags that are not
- * managed by this provider. Its attributes are exactly the same as the `vsphere.Tag`
- * resource, and, like importing, the data source takes a name and
- * category to search on. The `id` and other attributes are then populated with
- * the data found by the search.
+ * The `vsphere.Tag` data source can be used to reference tags that are not managed
+ * by Terraform. Its attributes are exactly the same as the
+ * [`vsphere.Tag` resource][resource-tag], and, like importing, the data source
+ * uses a name and category as search criteria. The `id` and other attributes are
+ * populated with the data found by the search.
+ *
+ * [resource-tag]: /docs/providers/vsphere/r/tag.html
  *
  * > **NOTE:** Tagging is not supported on direct ESXi hosts connections and
  * requires vCenter Server.

package/getTag.js

@@ -6,11 +6,13 @@ exports.getTagOutput = exports.getTag = void 0;
 const pulumi = require("@pulumi/pulumi");
 const utilities = require("./utilities");
 /**
- * The `vsphere.Tag` data source can be used to reference tags that are not
- * managed by this provider. Its attributes are exactly the same as the `vsphere.Tag`
- * resource, and, like importing, the data source takes a name and
- * category to search on. The `id` and other attributes are then populated with
- * the data found by the search.
+ * The `vsphere.Tag` data source can be used to reference tags that are not managed
+ * by Terraform. Its attributes are exactly the same as the
+ * [`vsphere.Tag` resource][resource-tag], and, like importing, the data source
+ * uses a name and category as search criteria. The `id` and other attributes are
+ * populated with the data found by the search.
+ *
+ * [resource-tag]: /docs/providers/vsphere/r/tag.html
  *
  * > **NOTE:** Tagging is not supported on direct ESXi hosts connections and
  * requires vCenter Server.
@@ -39,11 +41,13 @@ function getTag(args, opts) {
 }
 exports.getTag = getTag;
 /**
- * The `vsphere.Tag` data source can be used to reference tags that are not
- * managed by this provider. Its attributes are exactly the same as the `vsphere.Tag`
- * resource, and, like importing, the data source takes a name and
- * category to search on. The `id` and other attributes are then populated with
- * the data found by the search.
+ * The `vsphere.Tag` data source can be used to reference tags that are not managed
+ * by Terraform. Its attributes are exactly the same as the
+ * [`vsphere.Tag` resource][resource-tag], and, like importing, the data source
+ * uses a name and category as search criteria. The `id` and other attributes are
+ * populated with the data found by the search.
+ *
+ * [resource-tag]: /docs/providers/vsphere/r/tag.html
  *
  * > **NOTE:** Tagging is not supported on direct ESXi hosts connections and
  * requires vCenter Server.

package/getTag.js.map

@@ -1 +1 @@
-{"version":3,"file":"getTag.js","sourceRoot":"","sources":["../getTag.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,SAAgB,MAAM,CAAC,IAAgB,EAAE,IAA2B;IAChE,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,6BAA6B,EAAE;QACxD,YAAY,EAAE,IAAI,CAAC,UAAU;QAC7B,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,wBAMC;AA6BD;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,SAAgB,YAAY,CAAC,IAAsB,EAAE,IAAiC;IAClF,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,YAAY,CAAC,6BAA6B,EAAE;QAC9D,YAAY,EAAE,IAAI,CAAC,UAAU;QAC7B,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,oCAMC"}
+{"version":3,"file":"getTag.js","sourceRoot":"","sources":["../getTag.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AACH,SAAgB,MAAM,CAAC,IAAgB,EAAE,IAA2B;IAChE,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,6BAA6B,EAAE;QACxD,YAAY,EAAE,IAAI,CAAC,UAAU;QAC7B,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,wBAMC;AA6BD;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AACH,SAAgB,YAAY,CAAC,IAAsB,EAAE,IAAiC;IAClF,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,YAAY,CAAC,6BAA6B,EAAE;QAC9D,YAAY,EAAE,IAAI,CAAC,UAAU;QAC7B,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,oCAMC"}

package/getTagCategory.d.ts

@@ -1,11 +1,13 @@
 import * as pulumi from "@pulumi/pulumi";
 /**
  * The `vsphere.TagCategory` data source can be used to reference tag categories
- * that are not managed by this provider. Its attributes are the same as the
- * `vsphere.TagCategory` resource, and, like importing,
+ * that are not managed by Terraform. Its attributes are the same as the
+ * [`vsphere.TagCategory` resource][resource-tag-category], and, like importing,
  * the data source uses a name and category as search criteria. The `id` and other
  * attributes are populated with the data found by the search.
  *
+ * [resource-tag-category]: /docs/providers/vsphere/r/tag_category.html
+ *
  * > **NOTE:** Tagging is not supported on direct ESXi hosts connections and
  * requires vCenter Server.
  *
@@ -45,11 +47,13 @@ export interface GetTagCategoryResult {
 }
 /**
  * The `vsphere.TagCategory` data source can be used to reference tag categories
- * that are not managed by this provider. Its attributes are the same as the
- * `vsphere.TagCategory` resource, and, like importing,
+ * that are not managed by Terraform. Its attributes are the same as the
+ * [`vsphere.TagCategory` resource][resource-tag-category], and, like importing,
  * the data source uses a name and category as search criteria. The `id` and other
  * attributes are populated with the data found by the search.
  *
+ * [resource-tag-category]: /docs/providers/vsphere/r/tag_category.html
+ *
  * > **NOTE:** Tagging is not supported on direct ESXi hosts connections and
  * requires vCenter Server.
  *

package/getTagCategory.js

@@ -7,11 +7,13 @@ const pulumi = require("@pulumi/pulumi");
 const utilities = require("./utilities");
 /**
  * The `vsphere.TagCategory` data source can be used to reference tag categories
- * that are not managed by this provider. Its attributes are the same as the
- * `vsphere.TagCategory` resource, and, like importing,
+ * that are not managed by Terraform. Its attributes are the same as the
+ * [`vsphere.TagCategory` resource][resource-tag-category], and, like importing,
  * the data source uses a name and category as search criteria. The `id` and other
  * attributes are populated with the data found by the search.
  *
+ * [resource-tag-category]: /docs/providers/vsphere/r/tag_category.html
+ *
  * > **NOTE:** Tagging is not supported on direct ESXi hosts connections and
  * requires vCenter Server.
  *
@@ -35,11 +37,13 @@ function getTagCategory(args, opts) {
 exports.getTagCategory = getTagCategory;
 /**
  * The `vsphere.TagCategory` data source can be used to reference tag categories
- * that are not managed by this provider. Its attributes are the same as the
- * `vsphere.TagCategory` resource, and, like importing,
+ * that are not managed by Terraform. Its attributes are the same as the
+ * [`vsphere.TagCategory` resource][resource-tag-category], and, like importing,
  * the data source uses a name and category as search criteria. The `id` and other
  * attributes are populated with the data found by the search.
  *
+ * [resource-tag-category]: /docs/providers/vsphere/r/tag_category.html
+ *
  * > **NOTE:** Tagging is not supported on direct ESXi hosts connections and
  * requires vCenter Server.
  *

package/getTagCategory.js.map

@@ -1 +1 @@
-{"version":3,"file":"getTagCategory.js","sourceRoot":"","sources":["../getTagCategory.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,SAAgB,cAAc,CAAC,IAAwB,EAAE,IAA2B;IAChF,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,6CAA6C,EAAE;QACxE,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AALD,wCAKC;AAyBD;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,SAAgB,oBAAoB,CAAC,IAA8B,EAAE,IAAiC;IAClG,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,YAAY,CAAC,6CAA6C,EAAE;QAC9E,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AALD,oDAKC"}
+{"version":3,"file":"getTagCategory.js","sourceRoot":"","sources":["../getTagCategory.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,SAAgB,cAAc,CAAC,IAAwB,EAAE,IAA2B;IAChF,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,6CAA6C,EAAE;QACxE,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AALD,wCAKC;AAyBD;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,SAAgB,oBAAoB,CAAC,IAA8B,EAAE,IAAiC;IAClG,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,YAAY,CAAC,6CAA6C,EAAE;QAC9E,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AALD,oDAKC"}

package/getVappContainer.d.ts

@@ -3,7 +3,9 @@ import * as pulumi from "@pulumi/pulumi";
  * The `vsphere.VappContainer` data source can be used to discover the ID of a
  * vApp container in vSphere. This is useful to return the ID of a vApp container
  * that you want to use to create virtual machines in using the
- * `vsphere.VirtualMachine` resource.
+ * [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource.
+ *
+ * [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
  *
  * ## Example Usage
  *
@@ -26,8 +28,11 @@ export declare function getVappContainer(args: GetVappContainerArgs, opts?: pulu
  */
 export interface GetVappContainerArgs {
     /**
-     * The managed object reference ID
-     * of the datacenter in which the vApp container is located.
+     * The
+     * [managed object reference ID][docs-about-morefs] of the datacenter in which
+     * the vApp container is located.
+     *
+     * [docs-about-morefs]: /docs/providers/vsphere/index.html#use-of-managed-object-references-by-the-vsphere-provider
      */
     datacenterId: string;
     /**
@@ -51,7 +56,9 @@ export interface GetVappContainerResult {
  * The `vsphere.VappContainer` data source can be used to discover the ID of a
  * vApp container in vSphere. This is useful to return the ID of a vApp container
  * that you want to use to create virtual machines in using the
- * `vsphere.VirtualMachine` resource.
+ * [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource.
+ *
+ * [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
  *
  * ## Example Usage
  *
@@ -74,8 +81,11 @@ export declare function getVappContainerOutput(args: GetVappContainerOutputArgs,
  */
 export interface GetVappContainerOutputArgs {
     /**
-     * The managed object reference ID
-     * of the datacenter in which the vApp container is located.
+     * The
+     * [managed object reference ID][docs-about-morefs] of the datacenter in which
+     * the vApp container is located.
+     *
+     * [docs-about-morefs]: /docs/providers/vsphere/index.html#use-of-managed-object-references-by-the-vsphere-provider
      */
     datacenterId: pulumi.Input<string>;
     /**

package/getVappContainer.js

@@ -9,7 +9,9 @@ const utilities = require("./utilities");
  * The `vsphere.VappContainer` data source can be used to discover the ID of a
  * vApp container in vSphere. This is useful to return the ID of a vApp container
  * that you want to use to create virtual machines in using the
- * `vsphere.VirtualMachine` resource.
+ * [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource.
+ *
+ * [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
  *
  * ## Example Usage
  *
@@ -38,7 +40,9 @@ exports.getVappContainer = getVappContainer;
  * The `vsphere.VappContainer` data source can be used to discover the ID of a
  * vApp container in vSphere. This is useful to return the ID of a vApp container
  * that you want to use to create virtual machines in using the
- * `vsphere.VirtualMachine` resource.
+ * [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource.
+ *
+ * [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
  *
  * ## Example Usage
  *

package/getVappContainer.js.map

@@ -1 +1 @@
-{"version":3,"file":"getVappContainer.js","sourceRoot":"","sources":["../getVappContainer.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,SAAgB,gBAAgB,CAAC,IAA0B,EAAE,IAA2B;IACpF,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,iDAAiD,EAAE;QAC5E,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,4CAMC;AA6BD;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,SAAgB,sBAAsB,CAAC,IAAgC,EAAE,IAAiC;IACtG,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,YAAY,CAAC,iDAAiD,EAAE;QAClF,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,wDAMC"}
+{"version":3,"file":"getVappContainer.js","sourceRoot":"","sources":["../getVappContainer.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,SAAgB,gBAAgB,CAAC,IAA0B,EAAE,IAA2B;IACpF,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,iDAAiD,EAAE;QAC5E,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,4CAMC;AAgCD;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,SAAgB,sBAAsB,CAAC,IAAgC,EAAE,IAAiC;IACtG,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,YAAY,CAAC,iDAAiD,EAAE;QAClF,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,wDAMC"}

package/getVirtualMachine.d.ts

@@ -3,11 +3,13 @@ import * as inputs from "./types/input";
 import * as outputs from "./types/output";
 /**
  * The `vsphere.VirtualMachine` data source can be used to find the UUID of an
- * existing virtual machine or template. The most common purpose is for finding
- * the UUID of a template to be used as the source for cloning to a new
- * `vsphere.VirtualMachine` resource. It also
+ * existing virtual machine or template. The most common purpose is for finding the
+ * UUID of a template to be used as the source for cloning to a new
+ * [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource. It also
  * reads the guest ID so that can be supplied as well.
  *
+ * [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
+ *
  * ## Example Usage
  *
  * In the following example, a virtual machine template is returned by its unique
@@ -72,11 +74,11 @@ export interface GetVirtualMachineArgs {
     cpuShareCount?: number;
     cpuShareLevel?: string;
     /**
-     * The managed object reference
-     * ID of the datacenter the virtual machine is located in.
-     * This can be omitted if the search path used in `name` is an absolute path.
-     * For default datacenters, use the `id` attribute from an empty
-     * `vsphere.Datacenter` data source.
+     * The [managed object reference
+     * ID][docs-about-morefs] of the datacenter the virtual machine is located in.
+     * This can be omitted if the search path used in `name` is an absolute path. For
+     * default datacenters, use the `id` attribute from an empty `vsphere.Datacenter`
+     * data source.
      */
     datacenterId?: string;
     efiSecureBootEnabled?: boolean;
@@ -93,7 +95,10 @@ export interface GetVirtualMachineArgs {
      */
     firmware?: string;
     /**
-     * The name of the virtual machine folder where the virtual machine is located. The `name` argument is limited to 80 characters. If the `name` argument includes the full path to the virtual machine and exceeds the 80 characters limit, the `folder` folder argument can be used.
+     * The name of the virtual machine folder where the virtual
+     * machine is located. The `name` argument is limited to 80 characters. If the
+     * `name` argument includes the full path to the virtual machine and exceeds the
+     * 80 characters limit, the `folder` folder argument can be used.
      */
     folder?: string;
     /**
@@ -119,9 +124,9 @@ export interface GetVirtualMachineArgs {
     memoryShareLevel?: string;
     moid?: string;
     /**
-     * The name of the virtual machine. This can be a name or
-     * the full path relative to the datacenter. This is required if a UUID lookup
-     * is not performed.
+     * The name of the virtual machine. This can be a name or the
+     * full path relative to the datacenter. This is required if a UUID lookup is not
+     * performed.
      */
     name?: string;
     nestedHvEnabled?: boolean;
@@ -139,11 +144,17 @@ export interface GetVirtualMachineArgs {
      * The number of NVMe controllers to
      * scan for disk attributes and controller types on. Default: `1`.
      *
+     * [docs-about-morefs]: /docs/providers/vsphere/index.html#use-of-managed-object-references-by-the-vsphere-provider
+     *
      * > **NOTE:** For best results, ensure that all the disks on any templates you
-     * use with this data source reside on the primary controller, and leave this
-     * value at the default. See the `vsphere.VirtualMachine`
-     * resource documentation for the significance of this setting, specifically the
-     * additional requirements and notes for cloning section.
+     * use with this data source reside on the primary controller, and leave this value
+     * at the default. See the
+     * [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource
+     * documentation for the significance of this setting, specifically the
+     * [additional requirements and notes for cloning][docs-virtual-machine-resource-cloning]
+     * section.
+     *
+     * [docs-virtual-machine-resource-cloning]: /docs/providers/vsphere/r/virtual_machine.html#additional-requirements-and-notes-for-cloning
      */
     nvmeControllerScanCount?: number;
     replaceTrigger?: string;
@@ -164,8 +175,8 @@ export interface GetVirtualMachineArgs {
     syncTimeWithHostPeriodically?: boolean;
     toolsUpgradePolicy?: string;
     /**
-     * Specify this field for a UUID lookup, `name` and `datacenterId`
-     * are not required if this is specified.
+     * Specify this field for a UUID lookup, `name` and
+     * `datacenterId` are not required if this is specified.
      */
     uuid?: string;
     vapp?: inputs.GetVirtualMachineVapp;
@@ -334,11 +345,13 @@ export interface GetVirtualMachineResult {
 }
 /**
  * The `vsphere.VirtualMachine` data source can be used to find the UUID of an
- * existing virtual machine or template. The most common purpose is for finding
- * the UUID of a template to be used as the source for cloning to a new
- * `vsphere.VirtualMachine` resource. It also
+ * existing virtual machine or template. The most common purpose is for finding the
+ * UUID of a template to be used as the source for cloning to a new
+ * [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource. It also
  * reads the guest ID so that can be supplied as well.
  *
+ * [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
+ *
  * ## Example Usage
  *
  * In the following example, a virtual machine template is returned by its unique
@@ -403,11 +416,11 @@ export interface GetVirtualMachineOutputArgs {
     cpuShareCount?: pulumi.Input<number>;
     cpuShareLevel?: pulumi.Input<string>;
     /**
-     * The managed object reference
-     * ID of the datacenter the virtual machine is located in.
-     * This can be omitted if the search path used in `name` is an absolute path.
-     * For default datacenters, use the `id` attribute from an empty
-     * `vsphere.Datacenter` data source.
+     * The [managed object reference
+     * ID][docs-about-morefs] of the datacenter the virtual machine is located in.
+     * This can be omitted if the search path used in `name` is an absolute path. For
+     * default datacenters, use the `id` attribute from an empty `vsphere.Datacenter`
+     * data source.
      */
     datacenterId?: pulumi.Input<string>;
     efiSecureBootEnabled?: pulumi.Input<boolean>;
@@ -424,7 +437,10 @@ export interface GetVirtualMachineOutputArgs {
      */
     firmware?: pulumi.Input<string>;
     /**
-     * The name of the virtual machine folder where the virtual machine is located. The `name` argument is limited to 80 characters. If the `name` argument includes the full path to the virtual machine and exceeds the 80 characters limit, the `folder` folder argument can be used.
+     * The name of the virtual machine folder where the virtual
+     * machine is located. The `name` argument is limited to 80 characters. If the
+     * `name` argument includes the full path to the virtual machine and exceeds the
+     * 80 characters limit, the `folder` folder argument can be used.
      */
     folder?: pulumi.Input<string>;
     /**
@@ -450,9 +466,9 @@ export interface GetVirtualMachineOutputArgs {
     memoryShareLevel?: pulumi.Input<string>;
     moid?: pulumi.Input<string>;
     /**
-     * The name of the virtual machine. This can be a name or
-     * the full path relative to the datacenter. This is required if a UUID lookup
-     * is not performed.
+     * The name of the virtual machine. This can be a name or the
+     * full path relative to the datacenter. This is required if a UUID lookup is not
+     * performed.
      */
     name?: pulumi.Input<string>;
     nestedHvEnabled?: pulumi.Input<boolean>;
@@ -470,11 +486,17 @@ export interface GetVirtualMachineOutputArgs {
      * The number of NVMe controllers to
      * scan for disk attributes and controller types on. Default: `1`.
      *
+     * [docs-about-morefs]: /docs/providers/vsphere/index.html#use-of-managed-object-references-by-the-vsphere-provider
+     *
      * > **NOTE:** For best results, ensure that all the disks on any templates you
-     * use with this data source reside on the primary controller, and leave this
-     * value at the default. See the `vsphere.VirtualMachine`
-     * resource documentation for the significance of this setting, specifically the
-     * additional requirements and notes for cloning section.
+     * use with this data source reside on the primary controller, and leave this value
+     * at the default. See the
+     * [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource
+     * documentation for the significance of this setting, specifically the
+     * [additional requirements and notes for cloning][docs-virtual-machine-resource-cloning]
+     * section.
+     *
+     * [docs-virtual-machine-resource-cloning]: /docs/providers/vsphere/r/virtual_machine.html#additional-requirements-and-notes-for-cloning
      */
     nvmeControllerScanCount?: pulumi.Input<number>;
     replaceTrigger?: pulumi.Input<string>;
@@ -495,8 +517,8 @@ export interface GetVirtualMachineOutputArgs {
     syncTimeWithHostPeriodically?: pulumi.Input<boolean>;
     toolsUpgradePolicy?: pulumi.Input<string>;
     /**
-     * Specify this field for a UUID lookup, `name` and `datacenterId`
-     * are not required if this is specified.
+     * Specify this field for a UUID lookup, `name` and
+     * `datacenterId` are not required if this is specified.
      */
     uuid?: pulumi.Input<string>;
     vapp?: pulumi.Input<inputs.GetVirtualMachineVappArgs>;

package/getVirtualMachine.js

@@ -7,11 +7,13 @@ const pulumi = require("@pulumi/pulumi");
 const utilities = require("./utilities");
 /**
  * The `vsphere.VirtualMachine` data source can be used to find the UUID of an
- * existing virtual machine or template. The most common purpose is for finding
- * the UUID of a template to be used as the source for cloning to a new
- * `vsphere.VirtualMachine` resource. It also
+ * existing virtual machine or template. The most common purpose is for finding the
+ * UUID of a template to be used as the source for cloning to a new
+ * [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource. It also
  * reads the guest ID so that can be supplied as well.
  *
+ * [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
+ *
  * ## Example Usage
  *
  * In the following example, a virtual machine template is returned by its unique
@@ -115,11 +117,13 @@ function getVirtualMachine(args, opts) {
 exports.getVirtualMachine = getVirtualMachine;
 /**
  * The `vsphere.VirtualMachine` data source can be used to find the UUID of an
- * existing virtual machine or template. The most common purpose is for finding
- * the UUID of a template to be used as the source for cloning to a new
- * `vsphere.VirtualMachine` resource. It also
+ * existing virtual machine or template. The most common purpose is for finding the
+ * UUID of a template to be used as the source for cloning to a new
+ * [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource. It also
  * reads the guest ID so that can be supplied as well.
  *
+ * [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
+ *
  * ## Example Usage
  *
  * In the following example, a virtual machine template is returned by its unique