@pulumi/vsphere 4.16.2 → 4.16.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/computeCluster.d.ts +137 -67
- package/computeCluster.js +92 -46
- package/computeCluster.js.map +1 -1
- package/computeClusterHostGroup.d.ts +45 -25
- package/computeClusterHostGroup.js +21 -13
- package/computeClusterHostGroup.js.map +1 -1
- package/computeClusterVmAffinityRule.d.ts +32 -20
- package/computeClusterVmAffinityRule.js +20 -14
- package/computeClusterVmAffinityRule.js.map +1 -1
- package/computeClusterVmAntiAffinityRule.d.ts +40 -13
- package/computeClusterVmAntiAffinityRule.js +28 -7
- package/computeClusterVmAntiAffinityRule.js.map +1 -1
- package/computeClusterVmDependencyRule.d.ts +32 -24
- package/computeClusterVmDependencyRule.js +20 -18
- package/computeClusterVmDependencyRule.js.map +1 -1
- package/computeClusterVmGroup.d.ts +32 -23
- package/computeClusterVmGroup.js +8 -11
- package/computeClusterVmGroup.js.map +1 -1
- package/computeClusterVmHostRule.d.ts +36 -26
- package/computeClusterVmHostRule.js +24 -20
- package/computeClusterVmHostRule.js.map +1 -1
- package/configurationProfile.d.ts +88 -0
- package/configurationProfile.js +88 -0
- package/configurationProfile.js.map +1 -1
- package/contentLibrary.d.ts +6 -4
- package/contentLibrary.js +3 -1
- package/contentLibrary.js.map +1 -1
- package/contentLibraryItem.d.ts +3 -2
- package/contentLibraryItem.js +3 -2
- package/contentLibraryItem.js.map +1 -1
- package/customAttribute.d.ts +2 -3
- package/customAttribute.js +2 -3
- package/customAttribute.js.map +1 -1
- package/datacenter.d.ts +18 -8
- package/datacenter.js +4 -3
- package/datacenter.js.map +1 -1
- package/datastoreCluster.d.ts +37 -25
- package/datastoreCluster.js +10 -10
- package/datastoreCluster.js.map +1 -1
- package/datastoreClusterVmAntiAffinityRule.d.ts +37 -22
- package/datastoreClusterVmAntiAffinityRule.js +13 -13
- package/datastoreClusterVmAntiAffinityRule.js.map +1 -1
- package/distributedPortGroup.d.ts +19 -9
- package/distributedPortGroup.js +7 -6
- package/distributedPortGroup.js.map +1 -1
- package/distributedVirtualSwitch.d.ts +27 -10
- package/distributedVirtualSwitch.js +3 -4
- package/distributedVirtualSwitch.js.map +1 -1
- package/dpmHostOverride.d.ts +21 -16
- package/dpmHostOverride.js +9 -10
- package/dpmHostOverride.js.map +1 -1
- package/drsVmOverride.d.ts +22 -17
- package/drsVmOverride.js +10 -11
- package/drsVmOverride.js.map +1 -1
- package/entityPermissions.d.ts +58 -0
- package/entityPermissions.js +58 -0
- package/entityPermissions.js.map +1 -1
- package/file.d.ts +15 -0
- package/file.js +15 -0
- package/file.js.map +1 -1
- package/folder.d.ts +37 -19
- package/folder.js +7 -10
- package/folder.js.map +1 -1
- package/getComputeCluster.d.ts +35 -19
- package/getComputeCluster.js +24 -10
- package/getComputeCluster.js.map +1 -1
- package/getCustomAttribute.d.ts +10 -6
- package/getCustomAttribute.js +10 -6
- package/getCustomAttribute.js.map +1 -1
- package/getDatacenter.d.ts +10 -6
- package/getDatacenter.js +10 -6
- package/getDatacenter.js.map +1 -1
- package/getDatastore.d.ts +22 -16
- package/getDatastore.js +12 -8
- package/getDatastore.js.map +1 -1
- package/getDatastoreCluster.d.ts +24 -10
- package/getDatastoreCluster.js +20 -6
- package/getDatastoreCluster.js.map +1 -1
- package/getDistributedVirtualSwitch.d.ts +25 -19
- package/getDistributedVirtualSwitch.js +12 -8
- package/getDistributedVirtualSwitch.js.map +1 -1
- package/getHost.d.ts +23 -13
- package/getHost.js +8 -4
- package/getHost.js.map +1 -1
- package/getNetwork.d.ts +12 -8
- package/getNetwork.js.map +1 -1
- package/getOvfVmTemplate.d.ts +276 -0
- package/getOvfVmTemplate.js +276 -0
- package/getOvfVmTemplate.js.map +1 -1
- package/getResourcePool.d.ts +38 -26
- package/getResourcePool.js +16 -8
- package/getResourcePool.js.map +1 -1
- package/getTag.d.ts +14 -10
- package/getTag.js +14 -10
- package/getTag.js.map +1 -1
- package/getTagCategory.d.ts +8 -4
- package/getTagCategory.js +8 -4
- package/getTagCategory.js.map +1 -1
- package/getVappContainer.d.ts +16 -6
- package/getVappContainer.js +6 -2
- package/getVappContainer.js.map +1 -1
- package/getVirtualMachine.d.ts +58 -36
- package/getVirtualMachine.js +10 -6
- package/getVirtualMachine.js.map +1 -1
- package/getVmfsDisks.d.ts +12 -4
- package/getVmfsDisks.js +6 -2
- package/getVmfsDisks.js.map +1 -1
- package/haVmOverride.d.ts +8 -10
- package/haVmOverride.js +8 -10
- package/haVmOverride.js.map +1 -1
- package/host.d.ts +54 -80
- package/host.js +54 -80
- package/host.js.map +1 -1
- package/hostPortGroup.d.ts +21 -11
- package/hostPortGroup.js +8 -4
- package/hostPortGroup.js.map +1 -1
- package/hostVirtualSwitch.d.ts +21 -17
- package/hostVirtualSwitch.js +9 -11
- package/hostVirtualSwitch.js.map +1 -1
- package/nasDatastore.d.ts +48 -35
- package/nasDatastore.js +9 -8
- package/nasDatastore.js.map +1 -1
- package/package.json +2 -2
- package/resourcePool.d.ts +31 -7
- package/resourcePool.js +13 -1
- package/resourcePool.js.map +1 -1
- package/role.d.ts +31 -2
- package/role.js +31 -2
- package/role.js.map +1 -1
- package/storageDrsVmOverride.d.ts +40 -17
- package/storageDrsVmOverride.js +19 -8
- package/storageDrsVmOverride.js.map +1 -1
- package/tag.d.ts +16 -15
- package/tag.js +16 -15
- package/tag.js.map +1 -1
- package/tagCategory.d.ts +2 -3
- package/tagCategory.js +2 -3
- package/tagCategory.js.map +1 -1
- package/types/input.d.ts +5 -3
- package/types/output.d.ts +5 -3
- package/vappContainer.d.ts +21 -12
- package/vappContainer.js +0 -3
- package/vappContainer.js.map +1 -1
- package/vappEntity.d.ts +14 -11
- package/vappEntity.js +2 -5
- package/vappEntity.js.map +1 -1
- package/virtualDisk.d.ts +18 -10
- package/virtualDisk.js +9 -7
- package/virtualDisk.js.map +1 -1
- package/virtualMachine.d.ts +1102 -10
- package/virtualMachine.js +1056 -6
- package/virtualMachine.js.map +1 -1
- package/virtualMachineSnapshot.d.ts +2 -1
- package/virtualMachineSnapshot.js +2 -1
- package/virtualMachineSnapshot.js.map +1 -1
- package/vmfsDatastore.d.ts +54 -42
- package/vmfsDatastore.js +12 -15
- package/vmfsDatastore.js.map +1 -1
- package/vnic.d.ts +4 -3
- package/vnic.js +4 -3
- package/vnic.js.map +1 -1
package/getDatacenter.js
CHANGED
|
@@ -6,11 +6,13 @@ exports.getDatacenterOutput = exports.getDatacenter = void 0;
|
|
|
6
6
|
const pulumi = require("@pulumi/pulumi");
|
|
7
7
|
const utilities = require("./utilities");
|
|
8
8
|
/**
|
|
9
|
-
* The `vsphere.Datacenter` data source can be used to discover the ID of a
|
|
10
|
-
*
|
|
11
|
-
*
|
|
9
|
+
* The `vsphere.Datacenter` data source can be used to discover the ID of a vSphere
|
|
10
|
+
* datacenter object. This can then be used with resources or data sources that
|
|
11
|
+
* require a datacenter, such as the [`vsphere.Host`][data-source-vsphere-host]
|
|
12
12
|
* data source.
|
|
13
13
|
*
|
|
14
|
+
* [data-source-vsphere-host]: /docs/providers/vsphere/d/host.html
|
|
15
|
+
*
|
|
14
16
|
* ## Example Usage
|
|
15
17
|
*
|
|
16
18
|
* ```typescript
|
|
@@ -31,11 +33,13 @@ function getDatacenter(args, opts) {
|
|
|
31
33
|
}
|
|
32
34
|
exports.getDatacenter = getDatacenter;
|
|
33
35
|
/**
|
|
34
|
-
* The `vsphere.Datacenter` data source can be used to discover the ID of a
|
|
35
|
-
*
|
|
36
|
-
*
|
|
36
|
+
* The `vsphere.Datacenter` data source can be used to discover the ID of a vSphere
|
|
37
|
+
* datacenter object. This can then be used with resources or data sources that
|
|
38
|
+
* require a datacenter, such as the [`vsphere.Host`][data-source-vsphere-host]
|
|
37
39
|
* data source.
|
|
38
40
|
*
|
|
41
|
+
* [data-source-vsphere-host]: /docs/providers/vsphere/d/host.html
|
|
42
|
+
*
|
|
39
43
|
* ## Example Usage
|
|
40
44
|
*
|
|
41
45
|
* ```typescript
|
package/getDatacenter.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"getDatacenter.js","sourceRoot":"","sources":["../getDatacenter.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC
|
|
1
|
+
{"version":3,"file":"getDatacenter.js","sourceRoot":"","sources":["../getDatacenter.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;GAkBG;AACH,SAAgB,aAAa,CAAC,IAAwB,EAAE,IAA2B;IAC/E,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,2CAA2C,EAAE;QACtE,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,sCAMC;AAgCD;;;;;;;;;;;;;;;;;;GAkBG;AACH,SAAgB,mBAAmB,CAAC,IAA8B,EAAE,IAAiC;IACjG,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,2CAA2C,EAAE;QAC5E,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,kDAMC"}
|
package/getDatastore.d.ts
CHANGED
|
@@ -1,9 +1,11 @@
|
|
|
1
1
|
import * as pulumi from "@pulumi/pulumi";
|
|
2
2
|
/**
|
|
3
|
-
* The `vsphere.getDatastore` data source can be used to discover the ID of a
|
|
4
|
-
*
|
|
5
|
-
*
|
|
6
|
-
* `vsphere.VirtualMachine` resource.
|
|
3
|
+
* The `vsphere.getDatastore` data source can be used to discover the ID of a vSphere
|
|
4
|
+
* datastore object. This can then be used with resources or data sources that
|
|
5
|
+
* require a datastore. For example, to create virtual machines in using the
|
|
6
|
+
* [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource.
|
|
7
|
+
*
|
|
8
|
+
* [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
|
|
7
9
|
*
|
|
8
10
|
* ## Example Usage
|
|
9
11
|
*
|
|
@@ -26,10 +28,11 @@ export declare function getDatastore(args: GetDatastoreArgs, opts?: pulumi.Invok
|
|
|
26
28
|
*/
|
|
27
29
|
export interface GetDatastoreArgs {
|
|
28
30
|
/**
|
|
29
|
-
* The
|
|
30
|
-
*
|
|
31
|
-
*
|
|
32
|
-
* the `id` attribute from an
|
|
31
|
+
* The
|
|
32
|
+
* [managed object reference ID][docs-about-morefs] of the datacenter the
|
|
33
|
+
* datastore is located in. This can be omitted if the search path used in `name`
|
|
34
|
+
* is an absolute path. For default datacenters, use the `id` attribute from an
|
|
35
|
+
* empty `vsphere.Datacenter` data source.
|
|
33
36
|
*/
|
|
34
37
|
datacenterId?: string;
|
|
35
38
|
/**
|
|
@@ -65,10 +68,12 @@ export interface GetDatastoreResult {
|
|
|
65
68
|
};
|
|
66
69
|
}
|
|
67
70
|
/**
|
|
68
|
-
* The `vsphere.getDatastore` data source can be used to discover the ID of a
|
|
69
|
-
*
|
|
70
|
-
*
|
|
71
|
-
* `vsphere.VirtualMachine` resource.
|
|
71
|
+
* The `vsphere.getDatastore` data source can be used to discover the ID of a vSphere
|
|
72
|
+
* datastore object. This can then be used with resources or data sources that
|
|
73
|
+
* require a datastore. For example, to create virtual machines in using the
|
|
74
|
+
* [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource.
|
|
75
|
+
*
|
|
76
|
+
* [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
|
|
72
77
|
*
|
|
73
78
|
* ## Example Usage
|
|
74
79
|
*
|
|
@@ -91,10 +96,11 @@ export declare function getDatastoreOutput(args: GetDatastoreOutputArgs, opts?:
|
|
|
91
96
|
*/
|
|
92
97
|
export interface GetDatastoreOutputArgs {
|
|
93
98
|
/**
|
|
94
|
-
* The
|
|
95
|
-
*
|
|
96
|
-
*
|
|
97
|
-
* the `id` attribute from an
|
|
99
|
+
* The
|
|
100
|
+
* [managed object reference ID][docs-about-morefs] of the datacenter the
|
|
101
|
+
* datastore is located in. This can be omitted if the search path used in `name`
|
|
102
|
+
* is an absolute path. For default datacenters, use the `id` attribute from an
|
|
103
|
+
* empty `vsphere.Datacenter` data source.
|
|
98
104
|
*/
|
|
99
105
|
datacenterId?: pulumi.Input<string>;
|
|
100
106
|
/**
|
package/getDatastore.js
CHANGED
|
@@ -6,10 +6,12 @@ exports.getDatastoreOutput = exports.getDatastore = void 0;
|
|
|
6
6
|
const pulumi = require("@pulumi/pulumi");
|
|
7
7
|
const utilities = require("./utilities");
|
|
8
8
|
/**
|
|
9
|
-
* The `vsphere.getDatastore` data source can be used to discover the ID of a
|
|
10
|
-
*
|
|
11
|
-
*
|
|
12
|
-
* `vsphere.VirtualMachine` resource.
|
|
9
|
+
* The `vsphere.getDatastore` data source can be used to discover the ID of a vSphere
|
|
10
|
+
* datastore object. This can then be used with resources or data sources that
|
|
11
|
+
* require a datastore. For example, to create virtual machines in using the
|
|
12
|
+
* [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource.
|
|
13
|
+
*
|
|
14
|
+
* [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
|
|
13
15
|
*
|
|
14
16
|
* ## Example Usage
|
|
15
17
|
*
|
|
@@ -36,10 +38,12 @@ function getDatastore(args, opts) {
|
|
|
36
38
|
}
|
|
37
39
|
exports.getDatastore = getDatastore;
|
|
38
40
|
/**
|
|
39
|
-
* The `vsphere.getDatastore` data source can be used to discover the ID of a
|
|
40
|
-
*
|
|
41
|
-
*
|
|
42
|
-
* `vsphere.VirtualMachine` resource.
|
|
41
|
+
* The `vsphere.getDatastore` data source can be used to discover the ID of a vSphere
|
|
42
|
+
* datastore object. This can then be used with resources or data sources that
|
|
43
|
+
* require a datastore. For example, to create virtual machines in using the
|
|
44
|
+
* [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource.
|
|
45
|
+
*
|
|
46
|
+
* [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
|
|
43
47
|
*
|
|
44
48
|
* ## Example Usage
|
|
45
49
|
*
|
package/getDatastore.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"getDatastore.js","sourceRoot":"","sources":["../getDatastore.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC
|
|
1
|
+
{"version":3,"file":"getDatastore.js","sourceRoot":"","sources":["../getDatastore.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,SAAgB,YAAY,CAAC,IAAsB,EAAE,IAA2B;IAC5E,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,yCAAyC,EAAE;QACpE,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;QACjB,OAAO,EAAE,IAAI,CAAC,KAAK;KACtB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAPD,oCAOC;AA2CD;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,SAAgB,kBAAkB,CAAC,IAA4B,EAAE,IAAiC;IAC9F,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,YAAY,CAAC,yCAAyC,EAAE;QAC1E,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;QACjB,OAAO,EAAE,IAAI,CAAC,KAAK;KACtB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAPD,gDAOC"}
|
package/getDatastoreCluster.d.ts
CHANGED
|
@@ -1,9 +1,16 @@
|
|
|
1
1
|
import * as pulumi from "@pulumi/pulumi";
|
|
2
2
|
/**
|
|
3
3
|
* The `vsphere.DatastoreCluster` data source can be used to discover the ID of a
|
|
4
|
-
* vSphere datastore cluster object. This can then be used with resources or data
|
|
5
|
-
* that require a datastore. For example, to assign datastores using the
|
|
6
|
-
* `vsphere.NasDatastore` or
|
|
4
|
+
* vSphere datastore cluster object. This can then be used with resources or data
|
|
5
|
+
* sources that require a datastore. For example, to assign datastores using the
|
|
6
|
+
* [`vsphere.NasDatastore`][docs-nas-datastore-resource] or
|
|
7
|
+
* [`vsphere.VmfsDatastore`][docs-vmfs-datastore-resource] resources, or to create
|
|
8
|
+
* virtual machines in using the
|
|
9
|
+
* [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource.
|
|
10
|
+
*
|
|
11
|
+
* [docs-nas-datastore-resource]: /docs/providers/vsphere/r/nas_datastore.html
|
|
12
|
+
* [docs-vmfs-datastore-resource]: /docs/providers/vsphere/r/vmfs_datastore.html
|
|
13
|
+
* [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
|
|
7
14
|
*
|
|
8
15
|
* ## Example Usage
|
|
9
16
|
*
|
|
@@ -26,8 +33,8 @@ export declare function getDatastoreCluster(args: GetDatastoreClusterArgs, opts?
|
|
|
26
33
|
*/
|
|
27
34
|
export interface GetDatastoreClusterArgs {
|
|
28
35
|
/**
|
|
29
|
-
* The managed object reference
|
|
30
|
-
* ID of the datacenter the datastore cluster is located in.
|
|
36
|
+
* The [managed object reference
|
|
37
|
+
* ID][docs-about-morefs] of the datacenter the datastore cluster is located in.
|
|
31
38
|
* This can be omitted if the search path used in `name` is an absolute path.
|
|
32
39
|
* For default datacenters, use the id attribute from an empty
|
|
33
40
|
* `vsphere.Datacenter` data source.
|
|
@@ -56,9 +63,16 @@ export interface GetDatastoreClusterResult {
|
|
|
56
63
|
}
|
|
57
64
|
/**
|
|
58
65
|
* The `vsphere.DatastoreCluster` data source can be used to discover the ID of a
|
|
59
|
-
* vSphere datastore cluster object. This can then be used with resources or data
|
|
60
|
-
* that require a datastore. For example, to assign datastores using the
|
|
61
|
-
* `vsphere.NasDatastore` or
|
|
66
|
+
* vSphere datastore cluster object. This can then be used with resources or data
|
|
67
|
+
* sources that require a datastore. For example, to assign datastores using the
|
|
68
|
+
* [`vsphere.NasDatastore`][docs-nas-datastore-resource] or
|
|
69
|
+
* [`vsphere.VmfsDatastore`][docs-vmfs-datastore-resource] resources, or to create
|
|
70
|
+
* virtual machines in using the
|
|
71
|
+
* [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource.
|
|
72
|
+
*
|
|
73
|
+
* [docs-nas-datastore-resource]: /docs/providers/vsphere/r/nas_datastore.html
|
|
74
|
+
* [docs-vmfs-datastore-resource]: /docs/providers/vsphere/r/vmfs_datastore.html
|
|
75
|
+
* [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
|
|
62
76
|
*
|
|
63
77
|
* ## Example Usage
|
|
64
78
|
*
|
|
@@ -81,8 +95,8 @@ export declare function getDatastoreClusterOutput(args: GetDatastoreClusterOutpu
|
|
|
81
95
|
*/
|
|
82
96
|
export interface GetDatastoreClusterOutputArgs {
|
|
83
97
|
/**
|
|
84
|
-
* The managed object reference
|
|
85
|
-
* ID of the datacenter the datastore cluster is located in.
|
|
98
|
+
* The [managed object reference
|
|
99
|
+
* ID][docs-about-morefs] of the datacenter the datastore cluster is located in.
|
|
86
100
|
* This can be omitted if the search path used in `name` is an absolute path.
|
|
87
101
|
* For default datacenters, use the id attribute from an empty
|
|
88
102
|
* `vsphere.Datacenter` data source.
|
package/getDatastoreCluster.js
CHANGED
|
@@ -7,9 +7,16 @@ const pulumi = require("@pulumi/pulumi");
|
|
|
7
7
|
const utilities = require("./utilities");
|
|
8
8
|
/**
|
|
9
9
|
* The `vsphere.DatastoreCluster` data source can be used to discover the ID of a
|
|
10
|
-
* vSphere datastore cluster object. This can then be used with resources or data
|
|
11
|
-
* that require a datastore. For example, to assign datastores using the
|
|
12
|
-
* `vsphere.NasDatastore` or
|
|
10
|
+
* vSphere datastore cluster object. This can then be used with resources or data
|
|
11
|
+
* sources that require a datastore. For example, to assign datastores using the
|
|
12
|
+
* [`vsphere.NasDatastore`][docs-nas-datastore-resource] or
|
|
13
|
+
* [`vsphere.VmfsDatastore`][docs-vmfs-datastore-resource] resources, or to create
|
|
14
|
+
* virtual machines in using the
|
|
15
|
+
* [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource.
|
|
16
|
+
*
|
|
17
|
+
* [docs-nas-datastore-resource]: /docs/providers/vsphere/r/nas_datastore.html
|
|
18
|
+
* [docs-vmfs-datastore-resource]: /docs/providers/vsphere/r/vmfs_datastore.html
|
|
19
|
+
* [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
|
|
13
20
|
*
|
|
14
21
|
* ## Example Usage
|
|
15
22
|
*
|
|
@@ -36,9 +43,16 @@ function getDatastoreCluster(args, opts) {
|
|
|
36
43
|
exports.getDatastoreCluster = getDatastoreCluster;
|
|
37
44
|
/**
|
|
38
45
|
* The `vsphere.DatastoreCluster` data source can be used to discover the ID of a
|
|
39
|
-
* vSphere datastore cluster object. This can then be used with resources or data
|
|
40
|
-
* that require a datastore. For example, to assign datastores using the
|
|
41
|
-
* `vsphere.NasDatastore` or
|
|
46
|
+
* vSphere datastore cluster object. This can then be used with resources or data
|
|
47
|
+
* sources that require a datastore. For example, to assign datastores using the
|
|
48
|
+
* [`vsphere.NasDatastore`][docs-nas-datastore-resource] or
|
|
49
|
+
* [`vsphere.VmfsDatastore`][docs-vmfs-datastore-resource] resources, or to create
|
|
50
|
+
* virtual machines in using the
|
|
51
|
+
* [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource.
|
|
52
|
+
*
|
|
53
|
+
* [docs-nas-datastore-resource]: /docs/providers/vsphere/r/nas_datastore.html
|
|
54
|
+
* [docs-vmfs-datastore-resource]: /docs/providers/vsphere/r/vmfs_datastore.html
|
|
55
|
+
* [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
|
|
42
56
|
*
|
|
43
57
|
* ## Example Usage
|
|
44
58
|
*
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"getDatastoreCluster.js","sourceRoot":"","sources":["../getDatastoreCluster.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC
|
|
1
|
+
{"version":3,"file":"getDatastoreCluster.js","sourceRoot":"","sources":["../getDatastoreCluster.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,SAAgB,mBAAmB,CAAC,IAA6B,EAAE,IAA2B;IAC1F,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,uDAAuD,EAAE;QAClF,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,kDAMC;AAoCD;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,SAAgB,yBAAyB,CAAC,IAAmC,EAAE,IAAiC;IAC5G,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,YAAY,CAAC,uDAAuD,EAAE;QACxF,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,8DAMC"}
|
|
@@ -1,11 +1,13 @@
|
|
|
1
1
|
import * as pulumi from "@pulumi/pulumi";
|
|
2
2
|
/**
|
|
3
|
-
* The `vsphere.DistributedVirtualSwitch` data source can be used to discover
|
|
4
|
-
*
|
|
5
|
-
*
|
|
6
|
-
* `vsphere.DistributedPortGroup` resource, for which
|
|
3
|
+
* The `vsphere.DistributedVirtualSwitch` data source can be used to discover the
|
|
4
|
+
* ID and uplink data of a of a vSphere distributed switch (VDS). This can then be
|
|
5
|
+
* used with resources or data sources that require a VDS, such as the
|
|
6
|
+
* [`vsphere.DistributedPortGroup`][distributed-port-group] resource, for which
|
|
7
7
|
* an example is shown below.
|
|
8
8
|
*
|
|
9
|
+
* [distributed-port-group]: /docs/providers/vsphere/r/distributed_port_group.html
|
|
10
|
+
*
|
|
9
11
|
* > **NOTE:** This data source requires vCenter Server and is not available on
|
|
10
12
|
* direct ESXi host connections.
|
|
11
13
|
*
|
|
@@ -41,10 +43,11 @@ export declare function getDistributedVirtualSwitch(args: GetDistributedVirtualS
|
|
|
41
43
|
*/
|
|
42
44
|
export interface GetDistributedVirtualSwitchArgs {
|
|
43
45
|
/**
|
|
44
|
-
* The
|
|
45
|
-
* of the datacenter the VDS is
|
|
46
|
-
*
|
|
47
|
-
*
|
|
46
|
+
* The
|
|
47
|
+
* [managed object reference ID][docs-about-morefs] of the datacenter the VDS is
|
|
48
|
+
* located in. This can be omitted if the search path used in `name` is an
|
|
49
|
+
* absolute path. For default datacenters, use the `id` attribute from an empty
|
|
50
|
+
* `vsphere.Datacenter` data source.
|
|
48
51
|
*/
|
|
49
52
|
datacenterId?: string;
|
|
50
53
|
/**
|
|
@@ -63,20 +66,22 @@ export interface GetDistributedVirtualSwitchResult {
|
|
|
63
66
|
readonly id: string;
|
|
64
67
|
readonly name: string;
|
|
65
68
|
/**
|
|
66
|
-
* The list of the uplinks on this vSphere distributed switch, as per
|
|
67
|
-
* `uplinks` argument to the
|
|
68
|
-
* `vsphere.DistributedVirtualSwitch`
|
|
69
|
+
* The list of the uplinks on this vSphere distributed switch, as per
|
|
70
|
+
* the [`uplinks`][distributed-virtual-switch-uplinks] argument to the
|
|
71
|
+
* [`vsphere.DistributedVirtualSwitch`][distributed-virtual-switch-resource]
|
|
69
72
|
* resource.
|
|
70
73
|
*/
|
|
71
74
|
readonly uplinks: string[];
|
|
72
75
|
}
|
|
73
76
|
/**
|
|
74
|
-
* The `vsphere.DistributedVirtualSwitch` data source can be used to discover
|
|
75
|
-
*
|
|
76
|
-
*
|
|
77
|
-
* `vsphere.DistributedPortGroup` resource, for which
|
|
77
|
+
* The `vsphere.DistributedVirtualSwitch` data source can be used to discover the
|
|
78
|
+
* ID and uplink data of a of a vSphere distributed switch (VDS). This can then be
|
|
79
|
+
* used with resources or data sources that require a VDS, such as the
|
|
80
|
+
* [`vsphere.DistributedPortGroup`][distributed-port-group] resource, for which
|
|
78
81
|
* an example is shown below.
|
|
79
82
|
*
|
|
83
|
+
* [distributed-port-group]: /docs/providers/vsphere/r/distributed_port_group.html
|
|
84
|
+
*
|
|
80
85
|
* > **NOTE:** This data source requires vCenter Server and is not available on
|
|
81
86
|
* direct ESXi host connections.
|
|
82
87
|
*
|
|
@@ -112,10 +117,11 @@ export declare function getDistributedVirtualSwitchOutput(args: GetDistributedVi
|
|
|
112
117
|
*/
|
|
113
118
|
export interface GetDistributedVirtualSwitchOutputArgs {
|
|
114
119
|
/**
|
|
115
|
-
* The
|
|
116
|
-
* of the datacenter the VDS is
|
|
117
|
-
*
|
|
118
|
-
*
|
|
120
|
+
* The
|
|
121
|
+
* [managed object reference ID][docs-about-morefs] of the datacenter the VDS is
|
|
122
|
+
* located in. This can be omitted if the search path used in `name` is an
|
|
123
|
+
* absolute path. For default datacenters, use the `id` attribute from an empty
|
|
124
|
+
* `vsphere.Datacenter` data source.
|
|
119
125
|
*/
|
|
120
126
|
datacenterId?: pulumi.Input<string>;
|
|
121
127
|
/**
|
|
@@ -6,12 +6,14 @@ exports.getDistributedVirtualSwitchOutput = exports.getDistributedVirtualSwitch
|
|
|
6
6
|
const pulumi = require("@pulumi/pulumi");
|
|
7
7
|
const utilities = require("./utilities");
|
|
8
8
|
/**
|
|
9
|
-
* The `vsphere.DistributedVirtualSwitch` data source can be used to discover
|
|
10
|
-
*
|
|
11
|
-
*
|
|
12
|
-
* `vsphere.DistributedPortGroup` resource, for which
|
|
9
|
+
* The `vsphere.DistributedVirtualSwitch` data source can be used to discover the
|
|
10
|
+
* ID and uplink data of a of a vSphere distributed switch (VDS). This can then be
|
|
11
|
+
* used with resources or data sources that require a VDS, such as the
|
|
12
|
+
* [`vsphere.DistributedPortGroup`][distributed-port-group] resource, for which
|
|
13
13
|
* an example is shown below.
|
|
14
14
|
*
|
|
15
|
+
* [distributed-port-group]: /docs/providers/vsphere/r/distributed_port_group.html
|
|
16
|
+
*
|
|
15
17
|
* > **NOTE:** This data source requires vCenter Server and is not available on
|
|
16
18
|
* direct ESXi host connections.
|
|
17
19
|
*
|
|
@@ -50,12 +52,14 @@ function getDistributedVirtualSwitch(args, opts) {
|
|
|
50
52
|
}
|
|
51
53
|
exports.getDistributedVirtualSwitch = getDistributedVirtualSwitch;
|
|
52
54
|
/**
|
|
53
|
-
* The `vsphere.DistributedVirtualSwitch` data source can be used to discover
|
|
54
|
-
*
|
|
55
|
-
*
|
|
56
|
-
* `vsphere.DistributedPortGroup` resource, for which
|
|
55
|
+
* The `vsphere.DistributedVirtualSwitch` data source can be used to discover the
|
|
56
|
+
* ID and uplink data of a of a vSphere distributed switch (VDS). This can then be
|
|
57
|
+
* used with resources or data sources that require a VDS, such as the
|
|
58
|
+
* [`vsphere.DistributedPortGroup`][distributed-port-group] resource, for which
|
|
57
59
|
* an example is shown below.
|
|
58
60
|
*
|
|
61
|
+
* [distributed-port-group]: /docs/providers/vsphere/r/distributed_port_group.html
|
|
62
|
+
*
|
|
59
63
|
* > **NOTE:** This data source requires vCenter Server and is not available on
|
|
60
64
|
* direct ESXi host connections.
|
|
61
65
|
*
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"getDistributedVirtualSwitch.js","sourceRoot":"","sources":["../getDistributedVirtualSwitch.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC
|
|
1
|
+
{"version":3,"file":"getDistributedVirtualSwitch.js","sourceRoot":"","sources":["../getDistributedVirtualSwitch.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqCG;AACH,SAAgB,2BAA2B,CAAC,IAAqC,EAAE,IAA2B;IAC1G,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,uEAAuE,EAAE;QAClG,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,kEAMC;AAsCD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqCG;AACH,SAAgB,iCAAiC,CAAC,IAA2C,EAAE,IAAiC;IAC5H,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,YAAY,CAAC,uEAAuE,EAAE;QACxG,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,8EAMC"}
|
package/getHost.d.ts
CHANGED
|
@@ -1,8 +1,10 @@
|
|
|
1
1
|
import * as pulumi from "@pulumi/pulumi";
|
|
2
2
|
/**
|
|
3
3
|
* The `vsphere.Host` data source can be used to discover the ID of an ESXi host.
|
|
4
|
-
* This can then be used with resources or data sources that require an ESX
|
|
5
|
-
*
|
|
4
|
+
* This can then be used with resources or data sources that require an ESX host's
|
|
5
|
+
* [managed object reference ID][docs-about-morefs].
|
|
6
|
+
*
|
|
7
|
+
* [docs-about-morefs]: /docs/providers/vsphere/index.html#use-of-managed-object-references-by-the-vsphere-provider
|
|
6
8
|
*
|
|
7
9
|
* ## Example Usage
|
|
8
10
|
*
|
|
@@ -25,13 +27,16 @@ export declare function getHost(args: GetHostArgs, opts?: pulumi.InvokeOptions):
|
|
|
25
27
|
*/
|
|
26
28
|
export interface GetHostArgs {
|
|
27
29
|
/**
|
|
28
|
-
* The
|
|
29
|
-
* of a vSphere datacenter
|
|
30
|
+
* The
|
|
31
|
+
* [managed object reference ID][docs-about-morefs] of a vSphere datacenter
|
|
32
|
+
* object.
|
|
30
33
|
*/
|
|
31
34
|
datacenterId: string;
|
|
32
35
|
/**
|
|
33
|
-
* The name of the ESXI host. This can be a name or path.
|
|
34
|
-
*
|
|
36
|
+
* The name of the ESXI host. This can be a name or path. Can
|
|
37
|
+
* be omitted if there is only one host in your inventory.
|
|
38
|
+
*
|
|
39
|
+
* [docs-about-morefs]: /docs/providers/vsphere/index.html#use-of-managed-object-references-by-the-vsphere-provider
|
|
35
40
|
*
|
|
36
41
|
* > **NOTE:** When used against an ESXi host directly, this data source _always_
|
|
37
42
|
* returns the ESXi host's object ID, regardless of what is entered into `name`.
|
|
@@ -49,15 +54,17 @@ export interface GetHostResult {
|
|
|
49
54
|
readonly id: string;
|
|
50
55
|
readonly name?: string;
|
|
51
56
|
/**
|
|
52
|
-
* The managed object ID of the ESXi
|
|
57
|
+
* The [managed object ID][docs-about-morefs] of the ESXi
|
|
53
58
|
* host's root resource pool.
|
|
54
59
|
*/
|
|
55
60
|
readonly resourcePoolId: string;
|
|
56
61
|
}
|
|
57
62
|
/**
|
|
58
63
|
* The `vsphere.Host` data source can be used to discover the ID of an ESXi host.
|
|
59
|
-
* This can then be used with resources or data sources that require an ESX
|
|
60
|
-
*
|
|
64
|
+
* This can then be used with resources or data sources that require an ESX host's
|
|
65
|
+
* [managed object reference ID][docs-about-morefs].
|
|
66
|
+
*
|
|
67
|
+
* [docs-about-morefs]: /docs/providers/vsphere/index.html#use-of-managed-object-references-by-the-vsphere-provider
|
|
61
68
|
*
|
|
62
69
|
* ## Example Usage
|
|
63
70
|
*
|
|
@@ -80,13 +87,16 @@ export declare function getHostOutput(args: GetHostOutputArgs, opts?: pulumi.Inv
|
|
|
80
87
|
*/
|
|
81
88
|
export interface GetHostOutputArgs {
|
|
82
89
|
/**
|
|
83
|
-
* The
|
|
84
|
-
* of a vSphere datacenter
|
|
90
|
+
* The
|
|
91
|
+
* [managed object reference ID][docs-about-morefs] of a vSphere datacenter
|
|
92
|
+
* object.
|
|
85
93
|
*/
|
|
86
94
|
datacenterId: pulumi.Input<string>;
|
|
87
95
|
/**
|
|
88
|
-
* The name of the ESXI host. This can be a name or path.
|
|
89
|
-
*
|
|
96
|
+
* The name of the ESXI host. This can be a name or path. Can
|
|
97
|
+
* be omitted if there is only one host in your inventory.
|
|
98
|
+
*
|
|
99
|
+
* [docs-about-morefs]: /docs/providers/vsphere/index.html#use-of-managed-object-references-by-the-vsphere-provider
|
|
90
100
|
*
|
|
91
101
|
* > **NOTE:** When used against an ESXi host directly, this data source _always_
|
|
92
102
|
* returns the ESXi host's object ID, regardless of what is entered into `name`.
|
package/getHost.js
CHANGED
|
@@ -7,8 +7,10 @@ const pulumi = require("@pulumi/pulumi");
|
|
|
7
7
|
const utilities = require("./utilities");
|
|
8
8
|
/**
|
|
9
9
|
* The `vsphere.Host` data source can be used to discover the ID of an ESXi host.
|
|
10
|
-
* This can then be used with resources or data sources that require an ESX
|
|
11
|
-
*
|
|
10
|
+
* This can then be used with resources or data sources that require an ESX host's
|
|
11
|
+
* [managed object reference ID][docs-about-morefs].
|
|
12
|
+
*
|
|
13
|
+
* [docs-about-morefs]: /docs/providers/vsphere/index.html#use-of-managed-object-references-by-the-vsphere-provider
|
|
12
14
|
*
|
|
13
15
|
* ## Example Usage
|
|
14
16
|
*
|
|
@@ -35,8 +37,10 @@ function getHost(args, opts) {
|
|
|
35
37
|
exports.getHost = getHost;
|
|
36
38
|
/**
|
|
37
39
|
* The `vsphere.Host` data source can be used to discover the ID of an ESXi host.
|
|
38
|
-
* This can then be used with resources or data sources that require an ESX
|
|
39
|
-
*
|
|
40
|
+
* This can then be used with resources or data sources that require an ESX host's
|
|
41
|
+
* [managed object reference ID][docs-about-morefs].
|
|
42
|
+
*
|
|
43
|
+
* [docs-about-morefs]: /docs/providers/vsphere/index.html#use-of-managed-object-references-by-the-vsphere-provider
|
|
40
44
|
*
|
|
41
45
|
* ## Example Usage
|
|
42
46
|
*
|
package/getHost.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"getHost.js","sourceRoot":"","sources":["../getHost.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC
|
|
1
|
+
{"version":3,"file":"getHost.js","sourceRoot":"","sources":["../getHost.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,SAAgB,OAAO,CAAC,IAAiB,EAAE,IAA2B;IAClE,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,+BAA+B,EAAE;QAC1D,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,0BAMC;AAwCD;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,SAAgB,aAAa,CAAC,IAAuB,EAAE,IAAiC;IACpF,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,YAAY,CAAC,+BAA+B,EAAE;QAChE,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,sCAMC"}
|
package/getNetwork.d.ts
CHANGED
|
@@ -47,10 +47,11 @@ export declare function getNetwork(args: GetNetworkArgs, opts?: pulumi.InvokeOpt
|
|
|
47
47
|
*/
|
|
48
48
|
export interface GetNetworkArgs {
|
|
49
49
|
/**
|
|
50
|
-
* The
|
|
51
|
-
* of the datacenter the network
|
|
52
|
-
* search path used in `name` is an
|
|
53
|
-
* use the `id` attribute from an empty
|
|
50
|
+
* The
|
|
51
|
+
* [managed object reference ID][docs-about-morefs] of the datacenter the network
|
|
52
|
+
* is located in. This can be omitted if the search path used in `name` is an
|
|
53
|
+
* absolute path. For default datacenters, use the `id` attribute from an empty
|
|
54
|
+
* `vsphere.Datacenter` data source.
|
|
54
55
|
*/
|
|
55
56
|
datacenterId?: string;
|
|
56
57
|
/**
|
|
@@ -78,6 +79,7 @@ export interface GetNetworkArgs {
|
|
|
78
79
|
retryTimeout?: number;
|
|
79
80
|
/**
|
|
80
81
|
* Select a VPC scope for retrieval of VPC subnets.
|
|
82
|
+
* [docs-about-morefs]: /docs/providers/vsphere/index.html#use-of-managed-object-references-by-the-vsphere-provider
|
|
81
83
|
*/
|
|
82
84
|
vpcId?: string;
|
|
83
85
|
}
|
|
@@ -150,10 +152,11 @@ export declare function getNetworkOutput(args: GetNetworkOutputArgs, opts?: pulu
|
|
|
150
152
|
*/
|
|
151
153
|
export interface GetNetworkOutputArgs {
|
|
152
154
|
/**
|
|
153
|
-
* The
|
|
154
|
-
* of the datacenter the network
|
|
155
|
-
* search path used in `name` is an
|
|
156
|
-
* use the `id` attribute from an empty
|
|
155
|
+
* The
|
|
156
|
+
* [managed object reference ID][docs-about-morefs] of the datacenter the network
|
|
157
|
+
* is located in. This can be omitted if the search path used in `name` is an
|
|
158
|
+
* absolute path. For default datacenters, use the `id` attribute from an empty
|
|
159
|
+
* `vsphere.Datacenter` data source.
|
|
157
160
|
*/
|
|
158
161
|
datacenterId?: pulumi.Input<string>;
|
|
159
162
|
/**
|
|
@@ -181,6 +184,7 @@ export interface GetNetworkOutputArgs {
|
|
|
181
184
|
retryTimeout?: pulumi.Input<number>;
|
|
182
185
|
/**
|
|
183
186
|
* Select a VPC scope for retrieval of VPC subnets.
|
|
187
|
+
* [docs-about-morefs]: /docs/providers/vsphere/index.html#use-of-managed-object-references-by-the-vsphere-provider
|
|
184
188
|
*/
|
|
185
189
|
vpcId?: pulumi.Input<string>;
|
|
186
190
|
}
|
package/getNetwork.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"getNetwork.js","sourceRoot":"","sources":["../getNetwork.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AAGzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAuCG;AACH,SAAgB,UAAU,CAAC,IAAoB,EAAE,IAA2B;IACxE,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,qCAAqC,EAAE;QAChE,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,8BAA8B,EAAE,IAAI,CAAC,4BAA4B;QACjE,SAAS,EAAE,IAAI,CAAC,OAAO;QACvB,MAAM,EAAE,IAAI,CAAC,IAAI;QACjB,eAAe,EAAE,IAAI,CAAC,aAAa;QACnC,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,OAAO,EAAE,IAAI,CAAC,KAAK;KACtB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAXD,gCAWC;
|
|
1
|
+
{"version":3,"file":"getNetwork.js","sourceRoot":"","sources":["../getNetwork.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AAGzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAuCG;AACH,SAAgB,UAAU,CAAC,IAAoB,EAAE,IAA2B;IACxE,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,qCAAqC,EAAE;QAChE,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,8BAA8B,EAAE,IAAI,CAAC,4BAA4B;QACjE,SAAS,EAAE,IAAI,CAAC,OAAO;QACvB,MAAM,EAAE,IAAI,CAAC,IAAI;QACjB,eAAe,EAAE,IAAI,CAAC,aAAa;QACnC,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,OAAO,EAAE,IAAI,CAAC,KAAK;KACtB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAXD,gCAWC;AAmED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAuCG;AACH,SAAgB,gBAAgB,CAAC,IAA0B,EAAE,IAAiC;IAC1F,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,YAAY,CAAC,qCAAqC,EAAE;QACtE,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,8BAA8B,EAAE,IAAI,CAAC,4BAA4B;QACjE,SAAS,EAAE,IAAI,CAAC,OAAO;QACvB,MAAM,EAAE,IAAI,CAAC,IAAI;QACjB,eAAe,EAAE,IAAI,CAAC,aAAa;QACnC,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,OAAO,EAAE,IAAI,CAAC,KAAK;KACtB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAXD,4CAWC"}
|