@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/entityPermissions.js
CHANGED
|
@@ -5,6 +5,64 @@ Object.defineProperty(exports, "__esModule", { value: true });
|
|
|
5
5
|
exports.EntityPermissions = void 0;
|
|
6
6
|
const pulumi = require("@pulumi/pulumi");
|
|
7
7
|
const utilities = require("./utilities");
|
|
8
|
+
/**
|
|
9
|
+
* The `vsphere.EntityPermissions` resource can be used to create and manage
|
|
10
|
+
* entity permissions. Permissions can be created on an entity for a given user or
|
|
11
|
+
* group with the specified role.
|
|
12
|
+
*
|
|
13
|
+
* ## Example Usage
|
|
14
|
+
*
|
|
15
|
+
* This example creates entity permissions on the virtual machine VM1 for the user
|
|
16
|
+
* group DCClients with role Datastore consumer and for user group ExternalIDPUsers
|
|
17
|
+
* with role my_terraform_role. The `entityId` can be the managed object id (or
|
|
18
|
+
* uuid for some resources). The `entityType` is one of the managed object types
|
|
19
|
+
* which can be found from the managed object types section
|
|
20
|
+
* [here](https://developer.broadcom.com/xapis/vsphere-web-services-api/latest/).
|
|
21
|
+
* Keep the permissions sorted alphabetically, ignoring case on `userOrGroup` for
|
|
22
|
+
* a better user experience.
|
|
23
|
+
*
|
|
24
|
+
* ```typescript
|
|
25
|
+
* import * as pulumi from "@pulumi/pulumi";
|
|
26
|
+
* import * as vsphere from "@pulumi/vsphere";
|
|
27
|
+
*
|
|
28
|
+
* const datacenter = vsphere.getDatacenter({
|
|
29
|
+
* name: "Sample_DC_2",
|
|
30
|
+
* });
|
|
31
|
+
* const vm = datacenter.then(datacenter => vsphere.getVirtualMachine({
|
|
32
|
+
* name: "VM1",
|
|
33
|
+
* datacenterId: datacenter.id,
|
|
34
|
+
* }));
|
|
35
|
+
* const role1 = vsphere.getRole({
|
|
36
|
+
* label: "Datastore consumer (sample)",
|
|
37
|
+
* });
|
|
38
|
+
* const role2 = new vsphere.Role("role2", {
|
|
39
|
+
* name: "my_terraform_role",
|
|
40
|
+
* rolePrivileges: [
|
|
41
|
+
* "Alarm.Acknowledge",
|
|
42
|
+
* "Alarm.Create",
|
|
43
|
+
* "Datacenter.Move",
|
|
44
|
+
* ],
|
|
45
|
+
* });
|
|
46
|
+
* const p1 = new vsphere.EntityPermissions("p1", {
|
|
47
|
+
* entityId: vm.then(vm => vm.id),
|
|
48
|
+
* entityType: "VirtualMachine",
|
|
49
|
+
* permissions: [
|
|
50
|
+
* {
|
|
51
|
+
* userOrGroup: "vsphere.local\\DCClients",
|
|
52
|
+
* propagate: true,
|
|
53
|
+
* isGroup: true,
|
|
54
|
+
* roleId: role1.then(role1 => role1.id),
|
|
55
|
+
* },
|
|
56
|
+
* {
|
|
57
|
+
* userOrGroup: "vsphere.local\\ExternalIDPUsers",
|
|
58
|
+
* propagate: true,
|
|
59
|
+
* isGroup: true,
|
|
60
|
+
* roleId: role2.id,
|
|
61
|
+
* },
|
|
62
|
+
* ],
|
|
63
|
+
* });
|
|
64
|
+
* ```
|
|
65
|
+
*/
|
|
8
66
|
class EntityPermissions extends pulumi.CustomResource {
|
|
9
67
|
/**
|
|
10
68
|
* Get an existing EntityPermissions resource's state with the given name, ID, and optional extra
|
package/entityPermissions.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"entityPermissions.js","sourceRoot":"","sources":["../entityPermissions.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AAGzC,yCAAyC;AAEzC,MAAa,iBAAkB,SAAQ,MAAM,CAAC,cAAc;IACxD;;;;;;;;OAQG;IACI,MAAM,CAAC,GAAG,CAAC,IAAY,EAAE,EAA2B,EAAE,KAA8B,EAAE,IAAmC;QAC5H,OAAO,IAAI,iBAAiB,CAAC,IAAI,EAAO,KAAK,EAAE,EAAE,GAAG,IAAI,EAAE,EAAE,EAAE,EAAE,EAAE,CAAC,CAAC;IACxE,CAAC;IAKD;;;OAGG;IACI,MAAM,CAAC,UAAU,CAAC,GAAQ;QAC7B,IAAI,GAAG,KAAK,SAAS,IAAI,GAAG,KAAK,IAAI,EAAE;YACnC,OAAO,KAAK,CAAC;SAChB;QACD,OAAO,GAAG,CAAC,cAAc,CAAC,KAAK,iBAAiB,CAAC,YAAY,CAAC;IAClE,CAAC;IA4BD,YAAY,IAAY,EAAE,WAA4D,EAAE,IAAmC;QACvH,IAAI,cAAc,GAAkB,EAAE,CAAC;QACvC,IAAI,GAAG,IAAI,IAAI,EAAE,CAAC;QAClB,IAAI,IAAI,CAAC,EAAE,EAAE;YACT,MAAM,KAAK,GAAG,WAAiD,CAAC;YAChE,cAAc,CAAC,UAAU,CAAC,GAAG,KAAK,EAAE,QAAQ,CAAC;YAC7C,cAAc,CAAC,YAAY,CAAC,GAAG,KAAK,EAAE,UAAU,CAAC;YACjD,cAAc,CAAC,aAAa,CAAC,GAAG,KAAK,EAAE,WAAW,CAAC;SACtD;aAAM;YACH,MAAM,IAAI,GAAG,WAAgD,CAAC;YAC9D,IAAI,IAAI,EAAE,QAAQ,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBAC3C,MAAM,IAAI,KAAK,CAAC,sCAAsC,CAAC,CAAC;aAC3D;YACD,IAAI,IAAI,EAAE,UAAU,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBAC7C,MAAM,IAAI,KAAK,CAAC,wCAAwC,CAAC,CAAC;aAC7D;YACD,IAAI,IAAI,EAAE,WAAW,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBAC9C,MAAM,IAAI,KAAK,CAAC,yCAAyC,CAAC,CAAC;aAC9D;YACD,cAAc,CAAC,UAAU,CAAC,GAAG,IAAI,EAAE,QAAQ,CAAC;YAC5C,cAAc,CAAC,YAAY,CAAC,GAAG,IAAI,EAAE,UAAU,CAAC;YAChD,cAAc,CAAC,aAAa,CAAC,GAAG,IAAI,EAAE,WAAW,CAAC;SACrD;QACD,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,CAAC,CAAC;QACnE,KAAK,CAAC,iBAAiB,CAAC,YAAY,EAAE,IAAI,EAAE,cAAc,EAAE,IAAI,CAAC,CAAC;IACtE,CAAC;;AA/EL,8CAgFC;AAlEG,gBAAgB;AACO,8BAAY,GAAG,mDAAmD,CAAC"}
|
|
1
|
+
{"version":3,"file":"entityPermissions.js","sourceRoot":"","sources":["../entityPermissions.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AAGzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAyDG;AACH,MAAa,iBAAkB,SAAQ,MAAM,CAAC,cAAc;IACxD;;;;;;;;OAQG;IACI,MAAM,CAAC,GAAG,CAAC,IAAY,EAAE,EAA2B,EAAE,KAA8B,EAAE,IAAmC;QAC5H,OAAO,IAAI,iBAAiB,CAAC,IAAI,EAAO,KAAK,EAAE,EAAE,GAAG,IAAI,EAAE,EAAE,EAAE,EAAE,EAAE,CAAC,CAAC;IACxE,CAAC;IAKD;;;OAGG;IACI,MAAM,CAAC,UAAU,CAAC,GAAQ;QAC7B,IAAI,GAAG,KAAK,SAAS,IAAI,GAAG,KAAK,IAAI,EAAE;YACnC,OAAO,KAAK,CAAC;SAChB;QACD,OAAO,GAAG,CAAC,cAAc,CAAC,KAAK,iBAAiB,CAAC,YAAY,CAAC;IAClE,CAAC;IA4BD,YAAY,IAAY,EAAE,WAA4D,EAAE,IAAmC;QACvH,IAAI,cAAc,GAAkB,EAAE,CAAC;QACvC,IAAI,GAAG,IAAI,IAAI,EAAE,CAAC;QAClB,IAAI,IAAI,CAAC,EAAE,EAAE;YACT,MAAM,KAAK,GAAG,WAAiD,CAAC;YAChE,cAAc,CAAC,UAAU,CAAC,GAAG,KAAK,EAAE,QAAQ,CAAC;YAC7C,cAAc,CAAC,YAAY,CAAC,GAAG,KAAK,EAAE,UAAU,CAAC;YACjD,cAAc,CAAC,aAAa,CAAC,GAAG,KAAK,EAAE,WAAW,CAAC;SACtD;aAAM;YACH,MAAM,IAAI,GAAG,WAAgD,CAAC;YAC9D,IAAI,IAAI,EAAE,QAAQ,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBAC3C,MAAM,IAAI,KAAK,CAAC,sCAAsC,CAAC,CAAC;aAC3D;YACD,IAAI,IAAI,EAAE,UAAU,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBAC7C,MAAM,IAAI,KAAK,CAAC,wCAAwC,CAAC,CAAC;aAC7D;YACD,IAAI,IAAI,EAAE,WAAW,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBAC9C,MAAM,IAAI,KAAK,CAAC,yCAAyC,CAAC,CAAC;aAC9D;YACD,cAAc,CAAC,UAAU,CAAC,GAAG,IAAI,EAAE,QAAQ,CAAC;YAC5C,cAAc,CAAC,YAAY,CAAC,GAAG,IAAI,EAAE,UAAU,CAAC;YAChD,cAAc,CAAC,aAAa,CAAC,GAAG,IAAI,EAAE,WAAW,CAAC;SACrD;QACD,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,CAAC,CAAC;QACnE,KAAK,CAAC,iBAAiB,CAAC,YAAY,EAAE,IAAI,EAAE,cAAc,EAAE,IAAI,CAAC,CAAC;IACtE,CAAC;;AA/EL,8CAgFC;AAlEG,gBAAgB;AACO,8BAAY,GAAG,mDAAmD,CAAC"}
|
package/file.d.ts
CHANGED
|
@@ -1,7 +1,22 @@
|
|
|
1
1
|
import * as pulumi from "@pulumi/pulumi";
|
|
2
2
|
/**
|
|
3
|
+
* The `vsphere.File` resource can be used to upload files (such as ISOs and
|
|
4
|
+
* virtual disk files) from the host machine that Terraform is running on to a
|
|
5
|
+
* datastore. The resource can also be used to copy files between datastores, or
|
|
6
|
+
* from one location to another on the same datastore.
|
|
7
|
+
*
|
|
8
|
+
* Updates to destination parameters such as `datacenter`, `datastore`, or
|
|
9
|
+
* `destinationFile` will move the managed file a new destination based on the
|
|
10
|
+
* values of the new settings. If any source parameter is changed, such as
|
|
11
|
+
* `sourceDatastore`, `sourceDatacenter`, or `sourceFile`), the resource will
|
|
12
|
+
* be re-created. Depending on if destination parameters are being changed,
|
|
13
|
+
* this may result in the destination file either being overwritten or
|
|
14
|
+
* deleted from the previous location.
|
|
15
|
+
*
|
|
3
16
|
* ## Example Usage
|
|
4
17
|
*
|
|
18
|
+
* ### S
|
|
19
|
+
*
|
|
5
20
|
* ### Uploading a File
|
|
6
21
|
*
|
|
7
22
|
* ```typescript
|
package/file.js
CHANGED
|
@@ -6,8 +6,23 @@ exports.File = void 0;
|
|
|
6
6
|
const pulumi = require("@pulumi/pulumi");
|
|
7
7
|
const utilities = require("./utilities");
|
|
8
8
|
/**
|
|
9
|
+
* The `vsphere.File` resource can be used to upload files (such as ISOs and
|
|
10
|
+
* virtual disk files) from the host machine that Terraform is running on to a
|
|
11
|
+
* datastore. The resource can also be used to copy files between datastores, or
|
|
12
|
+
* from one location to another on the same datastore.
|
|
13
|
+
*
|
|
14
|
+
* Updates to destination parameters such as `datacenter`, `datastore`, or
|
|
15
|
+
* `destinationFile` will move the managed file a new destination based on the
|
|
16
|
+
* values of the new settings. If any source parameter is changed, such as
|
|
17
|
+
* `sourceDatastore`, `sourceDatacenter`, or `sourceFile`), the resource will
|
|
18
|
+
* be re-created. Depending on if destination parameters are being changed,
|
|
19
|
+
* this may result in the destination file either being overwritten or
|
|
20
|
+
* deleted from the previous location.
|
|
21
|
+
*
|
|
9
22
|
* ## Example Usage
|
|
10
23
|
*
|
|
24
|
+
* ### S
|
|
25
|
+
*
|
|
11
26
|
* ### Uploading a File
|
|
12
27
|
*
|
|
13
28
|
* ```typescript
|
package/file.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"file.js","sourceRoot":"","sources":["../file.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC
|
|
1
|
+
{"version":3,"file":"file.js","sourceRoot":"","sources":["../file.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAiDG;AACH,MAAa,IAAK,SAAQ,MAAM,CAAC,cAAc;IAC3C;;;;;;;;OAQG;IACI,MAAM,CAAC,GAAG,CAAC,IAAY,EAAE,EAA2B,EAAE,KAAiB,EAAE,IAAmC;QAC/G,OAAO,IAAI,IAAI,CAAC,IAAI,EAAO,KAAK,EAAE,EAAE,GAAG,IAAI,EAAE,EAAE,EAAE,EAAE,EAAE,CAAC,CAAC;IAC3D,CAAC;IAKD;;;OAGG;IACI,MAAM,CAAC,UAAU,CAAC,GAAQ;QAC7B,IAAI,GAAG,KAAK,SAAS,IAAI,GAAG,KAAK,IAAI,EAAE;YACnC,OAAO,KAAK,CAAC;SAChB;QACD,OAAO,GAAG,CAAC,cAAc,CAAC,KAAK,IAAI,CAAC,YAAY,CAAC;IACrD,CAAC;IA6CD,YAAY,IAAY,EAAE,WAAkC,EAAE,IAAmC;QAC7F,IAAI,cAAc,GAAkB,EAAE,CAAC;QACvC,IAAI,GAAG,IAAI,IAAI,EAAE,CAAC;QAClB,IAAI,IAAI,CAAC,EAAE,EAAE;YACT,MAAM,KAAK,GAAG,WAAoC,CAAC;YACnD,cAAc,CAAC,mBAAmB,CAAC,GAAG,KAAK,EAAE,iBAAiB,CAAC;YAC/D,cAAc,CAAC,YAAY,CAAC,GAAG,KAAK,EAAE,UAAU,CAAC;YACjD,cAAc,CAAC,WAAW,CAAC,GAAG,KAAK,EAAE,SAAS,CAAC;YAC/C,cAAc,CAAC,iBAAiB,CAAC,GAAG,KAAK,EAAE,eAAe,CAAC;YAC3D,cAAc,CAAC,kBAAkB,CAAC,GAAG,KAAK,EAAE,gBAAgB,CAAC;YAC7D,cAAc,CAAC,iBAAiB,CAAC,GAAG,KAAK,EAAE,eAAe,CAAC;YAC3D,cAAc,CAAC,YAAY,CAAC,GAAG,KAAK,EAAE,UAAU,CAAC;SACpD;aAAM;YACH,MAAM,IAAI,GAAG,WAAmC,CAAC;YACjD,IAAI,IAAI,EAAE,SAAS,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBAC5C,MAAM,IAAI,KAAK,CAAC,uCAAuC,CAAC,CAAC;aAC5D;YACD,IAAI,IAAI,EAAE,eAAe,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBAClD,MAAM,IAAI,KAAK,CAAC,6CAA6C,CAAC,CAAC;aAClE;YACD,IAAI,IAAI,EAAE,UAAU,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBAC7C,MAAM,IAAI,KAAK,CAAC,wCAAwC,CAAC,CAAC;aAC7D;YACD,cAAc,CAAC,mBAAmB,CAAC,GAAG,IAAI,EAAE,iBAAiB,CAAC;YAC9D,cAAc,CAAC,YAAY,CAAC,GAAG,IAAI,EAAE,UAAU,CAAC;YAChD,cAAc,CAAC,WAAW,CAAC,GAAG,IAAI,EAAE,SAAS,CAAC;YAC9C,cAAc,CAAC,iBAAiB,CAAC,GAAG,IAAI,EAAE,eAAe,CAAC;YAC1D,cAAc,CAAC,kBAAkB,CAAC,GAAG,IAAI,EAAE,gBAAgB,CAAC;YAC5D,cAAc,CAAC,iBAAiB,CAAC,GAAG,IAAI,EAAE,eAAe,CAAC;YAC1D,cAAc,CAAC,YAAY,CAAC,GAAG,IAAI,EAAE,UAAU,CAAC;SACnD;QACD,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,CAAC,CAAC;QACnE,KAAK,CAAC,IAAI,CAAC,YAAY,EAAE,IAAI,EAAE,cAAc,EAAE,IAAI,CAAC,CAAC;IACzD,CAAC;;AAxGL,oBAyGC;AA3FG,gBAAgB;AACO,iBAAY,GAAG,yBAAyB,CAAC"}
|
package/folder.d.ts
CHANGED
|
@@ -13,7 +13,7 @@ import * as pulumi from "@pulumi/pulumi";
|
|
|
13
13
|
* ## Example Usage
|
|
14
14
|
*
|
|
15
15
|
* The basic example below creates a virtual machine folder named
|
|
16
|
-
* `
|
|
16
|
+
* `example-vm-folder` in the default datacenter's VM hierarchy.
|
|
17
17
|
*
|
|
18
18
|
* ```typescript
|
|
19
19
|
* import * as pulumi from "@pulumi/pulumi";
|
|
@@ -22,8 +22,8 @@ import * as pulumi from "@pulumi/pulumi";
|
|
|
22
22
|
* const datacenter = vsphere.getDatacenter({
|
|
23
23
|
* name: vsphereDatacenter,
|
|
24
24
|
* });
|
|
25
|
-
* const
|
|
26
|
-
* path: "
|
|
25
|
+
* const vmFolder = new vsphere.Folder("vm_folder", {
|
|
26
|
+
* path: "example-vm-folder",
|
|
27
27
|
* type: "vm",
|
|
28
28
|
* datacenterId: datacenter.then(datacenter => datacenter.id),
|
|
29
29
|
* });
|
|
@@ -32,7 +32,7 @@ import * as pulumi from "@pulumi/pulumi";
|
|
|
32
32
|
* ### Example with Sub-folders
|
|
33
33
|
*
|
|
34
34
|
* The below example builds off of the above by first creating a folder named
|
|
35
|
-
* `
|
|
35
|
+
* `example-parent-vm-folder`, and then locating `example-child-vm-folder` in that
|
|
36
36
|
* folder. To ensure the parent is created first, we create an interpolation
|
|
37
37
|
* dependency off the parent's `path` attribute.
|
|
38
38
|
*
|
|
@@ -48,12 +48,12 @@ import * as pulumi from "@pulumi/pulumi";
|
|
|
48
48
|
* name: vsphereDatacenter,
|
|
49
49
|
* });
|
|
50
50
|
* const parent = new vsphere.Folder("parent", {
|
|
51
|
-
* path: "
|
|
51
|
+
* path: "example-parent-vm-folder",
|
|
52
52
|
* type: "vm",
|
|
53
53
|
* datacenterId: datacenter.then(datacenter => datacenter.id),
|
|
54
54
|
* });
|
|
55
|
-
* const
|
|
56
|
-
* path: pulumi.interpolate`${parent.path}/
|
|
55
|
+
* const child = new vsphere.Folder("child", {
|
|
56
|
+
* path: pulumi.interpolate`${parent.path}/example-child-vm-folder`,
|
|
57
57
|
* type: "vm",
|
|
58
58
|
* datacenterId: datacenter.then(datacenter => datacenter.id),
|
|
59
59
|
* });
|
|
@@ -62,7 +62,6 @@ import * as pulumi from "@pulumi/pulumi";
|
|
|
62
62
|
* ## Import
|
|
63
63
|
*
|
|
64
64
|
* An existing folder can be imported into this resource via
|
|
65
|
-
*
|
|
66
65
|
* its full path, via the following command:
|
|
67
66
|
*
|
|
68
67
|
* [docs-import]: https://developer.hashicorp.com/terraform/cli/import
|
|
@@ -72,9 +71,7 @@ import * as pulumi from "@pulumi/pulumi";
|
|
|
72
71
|
* ```
|
|
73
72
|
*
|
|
74
73
|
* The above command would import the folder from our examples above, the VM
|
|
75
|
-
*
|
|
76
74
|
* folder named `example-vm-folder` located in the datacenter named
|
|
77
|
-
*
|
|
78
75
|
* `default-dc`.
|
|
79
76
|
*/
|
|
80
77
|
export declare class Folder extends pulumi.CustomResource {
|
|
@@ -117,8 +114,12 @@ export declare class Folder extends pulumi.CustomResource {
|
|
|
117
114
|
* the root of the type of folder you are creating, and the supplied datacenter.
|
|
118
115
|
* For example, given a default datacenter of `default-dc`, a folder of type
|
|
119
116
|
* `vm` (denoting a virtual machine folder), and a supplied folder of
|
|
120
|
-
* `
|
|
121
|
-
* `/default-dc/vm/
|
|
117
|
+
* `example-vm-folder`, the resulting path would be
|
|
118
|
+
* `/default-dc/vm/example-vm-folder`.
|
|
119
|
+
*
|
|
120
|
+
* When working with nested datacenters, note that references to these folders in data sources
|
|
121
|
+
* will require the full path including the parent datacenter folder path, as shown in the
|
|
122
|
+
* nested datacenter example above.
|
|
122
123
|
*
|
|
123
124
|
* > **NOTE:** `path` can be modified - the resulting behavior is dependent on
|
|
124
125
|
* what section of `path` you are modifying. If you are modifying the parent (so
|
|
@@ -127,7 +128,10 @@ export declare class Folder extends pulumi.CustomResource {
|
|
|
127
128
|
*/
|
|
128
129
|
readonly path: pulumi.Output<string>;
|
|
129
130
|
/**
|
|
130
|
-
* The IDs of any tags to attach to this resource.
|
|
131
|
+
* The IDs of any tags to attach to this resource. See
|
|
132
|
+
* [here][docs-applying-tags] for a reference on how to apply tags.
|
|
133
|
+
*
|
|
134
|
+
* [docs-applying-tags]: /docs/providers/vsphere/r/tag.html#using-tags-in-a-supported-resource
|
|
131
135
|
*/
|
|
132
136
|
readonly tags: pulumi.Output<string[] | undefined>;
|
|
133
137
|
/**
|
|
@@ -174,8 +178,12 @@ export interface FolderState {
|
|
|
174
178
|
* the root of the type of folder you are creating, and the supplied datacenter.
|
|
175
179
|
* For example, given a default datacenter of `default-dc`, a folder of type
|
|
176
180
|
* `vm` (denoting a virtual machine folder), and a supplied folder of
|
|
177
|
-
* `
|
|
178
|
-
* `/default-dc/vm/
|
|
181
|
+
* `example-vm-folder`, the resulting path would be
|
|
182
|
+
* `/default-dc/vm/example-vm-folder`.
|
|
183
|
+
*
|
|
184
|
+
* When working with nested datacenters, note that references to these folders in data sources
|
|
185
|
+
* will require the full path including the parent datacenter folder path, as shown in the
|
|
186
|
+
* nested datacenter example above.
|
|
179
187
|
*
|
|
180
188
|
* > **NOTE:** `path` can be modified - the resulting behavior is dependent on
|
|
181
189
|
* what section of `path` you are modifying. If you are modifying the parent (so
|
|
@@ -184,7 +192,10 @@ export interface FolderState {
|
|
|
184
192
|
*/
|
|
185
193
|
path?: pulumi.Input<string>;
|
|
186
194
|
/**
|
|
187
|
-
* The IDs of any tags to attach to this resource.
|
|
195
|
+
* The IDs of any tags to attach to this resource. See
|
|
196
|
+
* [here][docs-applying-tags] for a reference on how to apply tags.
|
|
197
|
+
*
|
|
198
|
+
* [docs-applying-tags]: /docs/providers/vsphere/r/tag.html#using-tags-in-a-supported-resource
|
|
188
199
|
*/
|
|
189
200
|
tags?: pulumi.Input<pulumi.Input<string>[]>;
|
|
190
201
|
/**
|
|
@@ -223,8 +234,12 @@ export interface FolderArgs {
|
|
|
223
234
|
* the root of the type of folder you are creating, and the supplied datacenter.
|
|
224
235
|
* For example, given a default datacenter of `default-dc`, a folder of type
|
|
225
236
|
* `vm` (denoting a virtual machine folder), and a supplied folder of
|
|
226
|
-
* `
|
|
227
|
-
* `/default-dc/vm/
|
|
237
|
+
* `example-vm-folder`, the resulting path would be
|
|
238
|
+
* `/default-dc/vm/example-vm-folder`.
|
|
239
|
+
*
|
|
240
|
+
* When working with nested datacenters, note that references to these folders in data sources
|
|
241
|
+
* will require the full path including the parent datacenter folder path, as shown in the
|
|
242
|
+
* nested datacenter example above.
|
|
228
243
|
*
|
|
229
244
|
* > **NOTE:** `path` can be modified - the resulting behavior is dependent on
|
|
230
245
|
* what section of `path` you are modifying. If you are modifying the parent (so
|
|
@@ -233,7 +248,10 @@ export interface FolderArgs {
|
|
|
233
248
|
*/
|
|
234
249
|
path: pulumi.Input<string>;
|
|
235
250
|
/**
|
|
236
|
-
* The IDs of any tags to attach to this resource.
|
|
251
|
+
* The IDs of any tags to attach to this resource. See
|
|
252
|
+
* [here][docs-applying-tags] for a reference on how to apply tags.
|
|
253
|
+
*
|
|
254
|
+
* [docs-applying-tags]: /docs/providers/vsphere/r/tag.html#using-tags-in-a-supported-resource
|
|
237
255
|
*/
|
|
238
256
|
tags?: pulumi.Input<pulumi.Input<string>[]>;
|
|
239
257
|
/**
|
package/folder.js
CHANGED
|
@@ -19,7 +19,7 @@ const utilities = require("./utilities");
|
|
|
19
19
|
* ## Example Usage
|
|
20
20
|
*
|
|
21
21
|
* The basic example below creates a virtual machine folder named
|
|
22
|
-
* `
|
|
22
|
+
* `example-vm-folder` in the default datacenter's VM hierarchy.
|
|
23
23
|
*
|
|
24
24
|
* ```typescript
|
|
25
25
|
* import * as pulumi from "@pulumi/pulumi";
|
|
@@ -28,8 +28,8 @@ const utilities = require("./utilities");
|
|
|
28
28
|
* const datacenter = vsphere.getDatacenter({
|
|
29
29
|
* name: vsphereDatacenter,
|
|
30
30
|
* });
|
|
31
|
-
* const
|
|
32
|
-
* path: "
|
|
31
|
+
* const vmFolder = new vsphere.Folder("vm_folder", {
|
|
32
|
+
* path: "example-vm-folder",
|
|
33
33
|
* type: "vm",
|
|
34
34
|
* datacenterId: datacenter.then(datacenter => datacenter.id),
|
|
35
35
|
* });
|
|
@@ -38,7 +38,7 @@ const utilities = require("./utilities");
|
|
|
38
38
|
* ### Example with Sub-folders
|
|
39
39
|
*
|
|
40
40
|
* The below example builds off of the above by first creating a folder named
|
|
41
|
-
* `
|
|
41
|
+
* `example-parent-vm-folder`, and then locating `example-child-vm-folder` in that
|
|
42
42
|
* folder. To ensure the parent is created first, we create an interpolation
|
|
43
43
|
* dependency off the parent's `path` attribute.
|
|
44
44
|
*
|
|
@@ -54,12 +54,12 @@ const utilities = require("./utilities");
|
|
|
54
54
|
* name: vsphereDatacenter,
|
|
55
55
|
* });
|
|
56
56
|
* const parent = new vsphere.Folder("parent", {
|
|
57
|
-
* path: "
|
|
57
|
+
* path: "example-parent-vm-folder",
|
|
58
58
|
* type: "vm",
|
|
59
59
|
* datacenterId: datacenter.then(datacenter => datacenter.id),
|
|
60
60
|
* });
|
|
61
|
-
* const
|
|
62
|
-
* path: pulumi.interpolate`${parent.path}/
|
|
61
|
+
* const child = new vsphere.Folder("child", {
|
|
62
|
+
* path: pulumi.interpolate`${parent.path}/example-child-vm-folder`,
|
|
63
63
|
* type: "vm",
|
|
64
64
|
* datacenterId: datacenter.then(datacenter => datacenter.id),
|
|
65
65
|
* });
|
|
@@ -68,7 +68,6 @@ const utilities = require("./utilities");
|
|
|
68
68
|
* ## Import
|
|
69
69
|
*
|
|
70
70
|
* An existing folder can be imported into this resource via
|
|
71
|
-
*
|
|
72
71
|
* its full path, via the following command:
|
|
73
72
|
*
|
|
74
73
|
* [docs-import]: https://developer.hashicorp.com/terraform/cli/import
|
|
@@ -78,9 +77,7 @@ const utilities = require("./utilities");
|
|
|
78
77
|
* ```
|
|
79
78
|
*
|
|
80
79
|
* The above command would import the folder from our examples above, the VM
|
|
81
|
-
*
|
|
82
80
|
* folder named `example-vm-folder` located in the datacenter named
|
|
83
|
-
*
|
|
84
81
|
* `default-dc`.
|
|
85
82
|
*/
|
|
86
83
|
class Folder extends pulumi.CustomResource {
|
package/folder.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"folder.js","sourceRoot":"","sources":["../folder.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC
|
|
1
|
+
{"version":3,"file":"folder.js","sourceRoot":"","sources":["../folder.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA0EG;AACH,MAAa,MAAO,SAAQ,MAAM,CAAC,cAAc;IAC7C;;;;;;;;OAQG;IACI,MAAM,CAAC,GAAG,CAAC,IAAY,EAAE,EAA2B,EAAE,KAAmB,EAAE,IAAmC;QACjH,OAAO,IAAI,MAAM,CAAC,IAAI,EAAO,KAAK,EAAE,EAAE,GAAG,IAAI,EAAE,EAAE,EAAE,EAAE,EAAE,CAAC,CAAC;IAC7D,CAAC;IAKD;;;OAGG;IACI,MAAM,CAAC,UAAU,CAAC,GAAQ;QAC7B,IAAI,GAAG,KAAK,SAAS,IAAI,GAAG,KAAK,IAAI,EAAE;YACnC,OAAO,KAAK,CAAC;SAChB;QACD,OAAO,GAAG,CAAC,cAAc,CAAC,KAAK,MAAM,CAAC,YAAY,CAAC;IACvD,CAAC;IA4DD,YAAY,IAAY,EAAE,WAAsC,EAAE,IAAmC;QACjG,IAAI,cAAc,GAAkB,EAAE,CAAC;QACvC,IAAI,GAAG,IAAI,IAAI,EAAE,CAAC;QAClB,IAAI,IAAI,CAAC,EAAE,EAAE;YACT,MAAM,KAAK,GAAG,WAAsC,CAAC;YACrD,cAAc,CAAC,kBAAkB,CAAC,GAAG,KAAK,EAAE,gBAAgB,CAAC;YAC7D,cAAc,CAAC,cAAc,CAAC,GAAG,KAAK,EAAE,YAAY,CAAC;YACrD,cAAc,CAAC,MAAM,CAAC,GAAG,KAAK,EAAE,IAAI,CAAC;YACrC,cAAc,CAAC,MAAM,CAAC,GAAG,KAAK,EAAE,IAAI,CAAC;YACrC,cAAc,CAAC,MAAM,CAAC,GAAG,KAAK,EAAE,IAAI,CAAC;SACxC;aAAM;YACH,MAAM,IAAI,GAAG,WAAqC,CAAC;YACnD,IAAI,IAAI,EAAE,IAAI,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBACvC,MAAM,IAAI,KAAK,CAAC,kCAAkC,CAAC,CAAC;aACvD;YACD,IAAI,IAAI,EAAE,IAAI,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBACvC,MAAM,IAAI,KAAK,CAAC,kCAAkC,CAAC,CAAC;aACvD;YACD,cAAc,CAAC,kBAAkB,CAAC,GAAG,IAAI,EAAE,gBAAgB,CAAC;YAC5D,cAAc,CAAC,cAAc,CAAC,GAAG,IAAI,EAAE,YAAY,CAAC;YACpD,cAAc,CAAC,MAAM,CAAC,GAAG,IAAI,EAAE,IAAI,CAAC;YACpC,cAAc,CAAC,MAAM,CAAC,GAAG,IAAI,EAAE,IAAI,CAAC;YACpC,cAAc,CAAC,MAAM,CAAC,GAAG,IAAI,EAAE,IAAI,CAAC;SACvC;QACD,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,CAAC,CAAC;QACnE,KAAK,CAAC,MAAM,CAAC,YAAY,EAAE,IAAI,EAAE,cAAc,EAAE,IAAI,CAAC,CAAC;IAC3D,CAAC;;AAhHL,wBAiHC;AAnGG,gBAAgB;AACO,mBAAY,GAAG,6BAA6B,CAAC"}
|
package/getComputeCluster.d.ts
CHANGED
|
@@ -1,14 +1,21 @@
|
|
|
1
1
|
import * as pulumi from "@pulumi/pulumi";
|
|
2
2
|
/**
|
|
3
3
|
* The `vsphere.ComputeCluster` data source can be used to discover the ID of a
|
|
4
|
-
* cluster in vSphere. This is useful to fetch the ID of a cluster that you want
|
|
5
|
-
*
|
|
6
|
-
*
|
|
4
|
+
* cluster in vSphere. This is useful to fetch the ID of a cluster that you want to
|
|
5
|
+
* use for virtual machine placement via the
|
|
6
|
+
* [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource, allowing to
|
|
7
|
+
* specify the cluster's root resource pool directly versus using the alias
|
|
8
|
+
* available through the [`vsphere.ResourcePool`][docs-resource-pool-data-source]
|
|
7
9
|
* data source.
|
|
8
10
|
*
|
|
9
|
-
*
|
|
11
|
+
* [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
|
|
12
|
+
* [docs-resource-pool-data-source]: /docs/providers/vsphere/d/resource_pool.html
|
|
13
|
+
*
|
|
14
|
+
* > You may also wish to see the [`vsphere.ComputeCluster`][docs-compute-cluster-resource]
|
|
10
15
|
* resource for more information about clusters and how to managed the resource
|
|
11
|
-
* in
|
|
16
|
+
* in Terraform.
|
|
17
|
+
*
|
|
18
|
+
* [docs-compute-cluster-resource]: /docs/providers/vsphere/r/compute_cluster.html
|
|
12
19
|
*
|
|
13
20
|
* ## Example Usage
|
|
14
21
|
*
|
|
@@ -31,10 +38,11 @@ export declare function getComputeCluster(args: GetComputeClusterArgs, opts?: pu
|
|
|
31
38
|
*/
|
|
32
39
|
export interface GetComputeClusterArgs {
|
|
33
40
|
/**
|
|
34
|
-
* The
|
|
35
|
-
* of the datacenter the cluster
|
|
36
|
-
* search path used in `name` is an
|
|
37
|
-
* use the `id` attribute from an empty
|
|
41
|
+
* The
|
|
42
|
+
* [managed object reference ID][docs-about-morefs] of the datacenter the cluster
|
|
43
|
+
* is located in. This can be omitted if the search path used in `name` is an
|
|
44
|
+
* absolute path. For default datacenters, use the `id` attribute from an empty
|
|
45
|
+
* `vsphere.Datacenter` data source.
|
|
38
46
|
*/
|
|
39
47
|
datacenterId?: string;
|
|
40
48
|
/**
|
|
@@ -53,21 +61,28 @@ export interface GetComputeClusterResult {
|
|
|
53
61
|
readonly id: string;
|
|
54
62
|
readonly name: string;
|
|
55
63
|
/**
|
|
56
|
-
* The managed object reference ID of
|
|
64
|
+
* The [managed object reference ID][docs-about-morefs] of
|
|
57
65
|
* the root resource pool for the cluster.
|
|
58
66
|
*/
|
|
59
67
|
readonly resourcePoolId: string;
|
|
60
68
|
}
|
|
61
69
|
/**
|
|
62
70
|
* The `vsphere.ComputeCluster` data source can be used to discover the ID of a
|
|
63
|
-
* cluster in vSphere. This is useful to fetch the ID of a cluster that you want
|
|
64
|
-
*
|
|
65
|
-
*
|
|
71
|
+
* cluster in vSphere. This is useful to fetch the ID of a cluster that you want to
|
|
72
|
+
* use for virtual machine placement via the
|
|
73
|
+
* [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource, allowing to
|
|
74
|
+
* specify the cluster's root resource pool directly versus using the alias
|
|
75
|
+
* available through the [`vsphere.ResourcePool`][docs-resource-pool-data-source]
|
|
66
76
|
* data source.
|
|
67
77
|
*
|
|
68
|
-
*
|
|
78
|
+
* [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
|
|
79
|
+
* [docs-resource-pool-data-source]: /docs/providers/vsphere/d/resource_pool.html
|
|
80
|
+
*
|
|
81
|
+
* > You may also wish to see the [`vsphere.ComputeCluster`][docs-compute-cluster-resource]
|
|
69
82
|
* resource for more information about clusters and how to managed the resource
|
|
70
|
-
* in
|
|
83
|
+
* in Terraform.
|
|
84
|
+
*
|
|
85
|
+
* [docs-compute-cluster-resource]: /docs/providers/vsphere/r/compute_cluster.html
|
|
71
86
|
*
|
|
72
87
|
* ## Example Usage
|
|
73
88
|
*
|
|
@@ -90,10 +105,11 @@ export declare function getComputeClusterOutput(args: GetComputeClusterOutputArg
|
|
|
90
105
|
*/
|
|
91
106
|
export interface GetComputeClusterOutputArgs {
|
|
92
107
|
/**
|
|
93
|
-
* The
|
|
94
|
-
* of the datacenter the cluster
|
|
95
|
-
* search path used in `name` is an
|
|
96
|
-
* use the `id` attribute from an empty
|
|
108
|
+
* The
|
|
109
|
+
* [managed object reference ID][docs-about-morefs] of the datacenter the cluster
|
|
110
|
+
* is located in. This can be omitted if the search path used in `name` is an
|
|
111
|
+
* absolute path. For default datacenters, use the `id` attribute from an empty
|
|
112
|
+
* `vsphere.Datacenter` data source.
|
|
97
113
|
*/
|
|
98
114
|
datacenterId?: pulumi.Input<string>;
|
|
99
115
|
/**
|
package/getComputeCluster.js
CHANGED
|
@@ -7,14 +7,21 @@ const pulumi = require("@pulumi/pulumi");
|
|
|
7
7
|
const utilities = require("./utilities");
|
|
8
8
|
/**
|
|
9
9
|
* The `vsphere.ComputeCluster` data source can be used to discover the ID of a
|
|
10
|
-
* cluster in vSphere. This is useful to fetch the ID of a cluster that you want
|
|
11
|
-
*
|
|
12
|
-
*
|
|
10
|
+
* cluster in vSphere. This is useful to fetch the ID of a cluster that you want to
|
|
11
|
+
* use for virtual machine placement via the
|
|
12
|
+
* [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource, allowing to
|
|
13
|
+
* specify the cluster's root resource pool directly versus using the alias
|
|
14
|
+
* available through the [`vsphere.ResourcePool`][docs-resource-pool-data-source]
|
|
13
15
|
* data source.
|
|
14
16
|
*
|
|
15
|
-
*
|
|
17
|
+
* [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
|
|
18
|
+
* [docs-resource-pool-data-source]: /docs/providers/vsphere/d/resource_pool.html
|
|
19
|
+
*
|
|
20
|
+
* > You may also wish to see the [`vsphere.ComputeCluster`][docs-compute-cluster-resource]
|
|
16
21
|
* resource for more information about clusters and how to managed the resource
|
|
17
|
-
* in
|
|
22
|
+
* in Terraform.
|
|
23
|
+
*
|
|
24
|
+
* [docs-compute-cluster-resource]: /docs/providers/vsphere/r/compute_cluster.html
|
|
18
25
|
*
|
|
19
26
|
* ## Example Usage
|
|
20
27
|
*
|
|
@@ -41,14 +48,21 @@ function getComputeCluster(args, opts) {
|
|
|
41
48
|
exports.getComputeCluster = getComputeCluster;
|
|
42
49
|
/**
|
|
43
50
|
* The `vsphere.ComputeCluster` data source can be used to discover the ID of a
|
|
44
|
-
* cluster in vSphere. This is useful to fetch the ID of a cluster that you want
|
|
45
|
-
*
|
|
46
|
-
*
|
|
51
|
+
* cluster in vSphere. This is useful to fetch the ID of a cluster that you want to
|
|
52
|
+
* use for virtual machine placement via the
|
|
53
|
+
* [`vsphere.VirtualMachine`][docs-virtual-machine-resource] resource, allowing to
|
|
54
|
+
* specify the cluster's root resource pool directly versus using the alias
|
|
55
|
+
* available through the [`vsphere.ResourcePool`][docs-resource-pool-data-source]
|
|
47
56
|
* data source.
|
|
48
57
|
*
|
|
49
|
-
*
|
|
58
|
+
* [docs-virtual-machine-resource]: /docs/providers/vsphere/r/virtual_machine.html
|
|
59
|
+
* [docs-resource-pool-data-source]: /docs/providers/vsphere/d/resource_pool.html
|
|
60
|
+
*
|
|
61
|
+
* > You may also wish to see the [`vsphere.ComputeCluster`][docs-compute-cluster-resource]
|
|
50
62
|
* resource for more information about clusters and how to managed the resource
|
|
51
|
-
* in
|
|
63
|
+
* in Terraform.
|
|
64
|
+
*
|
|
65
|
+
* [docs-compute-cluster-resource]: /docs/providers/vsphere/r/compute_cluster.html
|
|
52
66
|
*
|
|
53
67
|
* ## Example Usage
|
|
54
68
|
*
|
package/getComputeCluster.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"getComputeCluster.js","sourceRoot":"","sources":["../getComputeCluster.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC
|
|
1
|
+
{"version":3,"file":"getComputeCluster.js","sourceRoot":"","sources":["../getComputeCluster.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgCG;AACH,SAAgB,iBAAiB,CAAC,IAA2B,EAAE,IAA2B;IACtF,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,mDAAmD,EAAE;QAC9E,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,8CAMC;AAoCD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgCG;AACH,SAAgB,uBAAuB,CAAC,IAAiC,EAAE,IAAiC;IACxG,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,YAAY,CAAC,mDAAmD,EAAE;QACpF,cAAc,EAAE,IAAI,CAAC,YAAY;QACjC,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AAND,0DAMC"}
|
package/getCustomAttribute.d.ts
CHANGED
|
@@ -1,11 +1,13 @@
|
|
|
1
1
|
import * as pulumi from "@pulumi/pulumi";
|
|
2
2
|
/**
|
|
3
3
|
* The `vsphere.CustomAttribute` data source can be used to reference custom
|
|
4
|
-
* attributes that are not managed by
|
|
5
|
-
* same as the `vsphere.CustomAttribute` resource,
|
|
4
|
+
* attributes that are not managed by Terraform. Its attributes are exactly the
|
|
5
|
+
* same as the [`vsphere.CustomAttribute` resource][resource-custom-attribute],
|
|
6
6
|
* and, like importing, the data source takes a name argument for the search. The
|
|
7
7
|
* `id` and other attributes are then populated with the data found by the search.
|
|
8
8
|
*
|
|
9
|
+
* [resource-custom-attribute]: /docs/providers/vsphere/r/custom_attribute.html
|
|
10
|
+
*
|
|
9
11
|
* > **NOTE:** Custom attributes are unsupported on direct ESXi host connections
|
|
10
12
|
* and require vCenter Server.
|
|
11
13
|
*
|
|
@@ -16,7 +18,7 @@ import * as pulumi from "@pulumi/pulumi";
|
|
|
16
18
|
* import * as vsphere from "@pulumi/vsphere";
|
|
17
19
|
*
|
|
18
20
|
* const attribute = vsphere.getCustomAttribute({
|
|
19
|
-
* name: "test-attribute",
|
|
21
|
+
* name: "pulumi-test-attribute",
|
|
20
22
|
* });
|
|
21
23
|
* ```
|
|
22
24
|
*/
|
|
@@ -43,11 +45,13 @@ export interface GetCustomAttributeResult {
|
|
|
43
45
|
}
|
|
44
46
|
/**
|
|
45
47
|
* The `vsphere.CustomAttribute` data source can be used to reference custom
|
|
46
|
-
* attributes that are not managed by
|
|
47
|
-
* same as the `vsphere.CustomAttribute` resource,
|
|
48
|
+
* attributes that are not managed by Terraform. Its attributes are exactly the
|
|
49
|
+
* same as the [`vsphere.CustomAttribute` resource][resource-custom-attribute],
|
|
48
50
|
* and, like importing, the data source takes a name argument for the search. The
|
|
49
51
|
* `id` and other attributes are then populated with the data found by the search.
|
|
50
52
|
*
|
|
53
|
+
* [resource-custom-attribute]: /docs/providers/vsphere/r/custom_attribute.html
|
|
54
|
+
*
|
|
51
55
|
* > **NOTE:** Custom attributes are unsupported on direct ESXi host connections
|
|
52
56
|
* and require vCenter Server.
|
|
53
57
|
*
|
|
@@ -58,7 +62,7 @@ export interface GetCustomAttributeResult {
|
|
|
58
62
|
* import * as vsphere from "@pulumi/vsphere";
|
|
59
63
|
*
|
|
60
64
|
* const attribute = vsphere.getCustomAttribute({
|
|
61
|
-
* name: "test-attribute",
|
|
65
|
+
* name: "pulumi-test-attribute",
|
|
62
66
|
* });
|
|
63
67
|
* ```
|
|
64
68
|
*/
|
package/getCustomAttribute.js
CHANGED
|
@@ -7,11 +7,13 @@ const pulumi = require("@pulumi/pulumi");
|
|
|
7
7
|
const utilities = require("./utilities");
|
|
8
8
|
/**
|
|
9
9
|
* The `vsphere.CustomAttribute` data source can be used to reference custom
|
|
10
|
-
* attributes that are not managed by
|
|
11
|
-
* same as the `vsphere.CustomAttribute` resource,
|
|
10
|
+
* attributes that are not managed by Terraform. Its attributes are exactly the
|
|
11
|
+
* same as the [`vsphere.CustomAttribute` resource][resource-custom-attribute],
|
|
12
12
|
* and, like importing, the data source takes a name argument for the search. The
|
|
13
13
|
* `id` and other attributes are then populated with the data found by the search.
|
|
14
14
|
*
|
|
15
|
+
* [resource-custom-attribute]: /docs/providers/vsphere/r/custom_attribute.html
|
|
16
|
+
*
|
|
15
17
|
* > **NOTE:** Custom attributes are unsupported on direct ESXi host connections
|
|
16
18
|
* and require vCenter Server.
|
|
17
19
|
*
|
|
@@ -22,7 +24,7 @@ const utilities = require("./utilities");
|
|
|
22
24
|
* import * as vsphere from "@pulumi/vsphere";
|
|
23
25
|
*
|
|
24
26
|
* const attribute = vsphere.getCustomAttribute({
|
|
25
|
-
* name: "test-attribute",
|
|
27
|
+
* name: "pulumi-test-attribute",
|
|
26
28
|
* });
|
|
27
29
|
* ```
|
|
28
30
|
*/
|
|
@@ -35,11 +37,13 @@ function getCustomAttribute(args, opts) {
|
|
|
35
37
|
exports.getCustomAttribute = getCustomAttribute;
|
|
36
38
|
/**
|
|
37
39
|
* The `vsphere.CustomAttribute` data source can be used to reference custom
|
|
38
|
-
* attributes that are not managed by
|
|
39
|
-
* same as the `vsphere.CustomAttribute` resource,
|
|
40
|
+
* attributes that are not managed by Terraform. Its attributes are exactly the
|
|
41
|
+
* same as the [`vsphere.CustomAttribute` resource][resource-custom-attribute],
|
|
40
42
|
* and, like importing, the data source takes a name argument for the search. The
|
|
41
43
|
* `id` and other attributes are then populated with the data found by the search.
|
|
42
44
|
*
|
|
45
|
+
* [resource-custom-attribute]: /docs/providers/vsphere/r/custom_attribute.html
|
|
46
|
+
*
|
|
43
47
|
* > **NOTE:** Custom attributes are unsupported on direct ESXi host connections
|
|
44
48
|
* and require vCenter Server.
|
|
45
49
|
*
|
|
@@ -50,7 +54,7 @@ exports.getCustomAttribute = getCustomAttribute;
|
|
|
50
54
|
* import * as vsphere from "@pulumi/vsphere";
|
|
51
55
|
*
|
|
52
56
|
* const attribute = vsphere.getCustomAttribute({
|
|
53
|
-
* name: "test-attribute",
|
|
57
|
+
* name: "pulumi-test-attribute",
|
|
54
58
|
* });
|
|
55
59
|
* ```
|
|
56
60
|
*/
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"getCustomAttribute.js","sourceRoot":"","sources":["../getCustomAttribute.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC
|
|
1
|
+
{"version":3,"file":"getCustomAttribute.js","sourceRoot":"","sources":["../getCustomAttribute.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,SAAgB,kBAAkB,CAAC,IAA4B,EAAE,IAA2B;IACxF,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,qDAAqD,EAAE;QAChF,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AALD,gDAKC;AAuBD;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,SAAgB,wBAAwB,CAAC,IAAkC,EAAE,IAAiC;IAC1G,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,IAAI,EAAE,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,OAAO,CAAC,YAAY,CAAC,qDAAqD,EAAE;QACtF,MAAM,EAAE,IAAI,CAAC,IAAI;KACpB,EAAE,IAAI,CAAC,CAAC;AACb,CAAC;AALD,4DAKC"}
|
package/getDatacenter.d.ts
CHANGED
|
@@ -1,10 +1,12 @@
|
|
|
1
1
|
import * as pulumi from "@pulumi/pulumi";
|
|
2
2
|
/**
|
|
3
|
-
* The `vsphere.Datacenter` data source can be used to discover the ID of a
|
|
4
|
-
*
|
|
5
|
-
*
|
|
3
|
+
* The `vsphere.Datacenter` data source can be used to discover the ID of a vSphere
|
|
4
|
+
* datacenter object. This can then be used with resources or data sources that
|
|
5
|
+
* require a datacenter, such as the [`vsphere.Host`][data-source-vsphere-host]
|
|
6
6
|
* data source.
|
|
7
7
|
*
|
|
8
|
+
* [data-source-vsphere-host]: /docs/providers/vsphere/d/host.html
|
|
9
|
+
*
|
|
8
10
|
* ## Example Usage
|
|
9
11
|
*
|
|
10
12
|
* ```typescript
|
|
@@ -47,11 +49,13 @@ export interface GetDatacenterResult {
|
|
|
47
49
|
readonly virtualMachines: string[];
|
|
48
50
|
}
|
|
49
51
|
/**
|
|
50
|
-
* The `vsphere.Datacenter` data source can be used to discover the ID of a
|
|
51
|
-
*
|
|
52
|
-
*
|
|
52
|
+
* The `vsphere.Datacenter` data source can be used to discover the ID of a vSphere
|
|
53
|
+
* datacenter object. This can then be used with resources or data sources that
|
|
54
|
+
* require a datacenter, such as the [`vsphere.Host`][data-source-vsphere-host]
|
|
53
55
|
* data source.
|
|
54
56
|
*
|
|
57
|
+
* [data-source-vsphere-host]: /docs/providers/vsphere/d/host.html
|
|
58
|
+
*
|
|
55
59
|
* ## Example Usage
|
|
56
60
|
*
|
|
57
61
|
* ```typescript
|