-
Notifications
You must be signed in to change notification settings - Fork 33
Show all the data in the state file that is returned from a deployment resource GET #41
Comments
Hello @Prativa20, My only concern is that we can pass the field ip_address to the next resource. For example: And for that reason, we cannot use this version to connect to a vm: resource "null_resource" "echo_hello_world" { provisioner "file" { Another great improvement to this provider would be the capability to use the storage tab. To conclude, the output of information is very important and the more output the better. However, It would be great if we could maintain the same output structure so that if we add more outputs we don't change the structure of the json. The automation I built is looking for a resource_configuration key to get the NETWORK_LIST.0.IP_ADDRESS, if in this new version we change that key to resources that is going to break all my automation. |
@Prativa20 Is there a build for Windows of the vra7 provider for the PR #40 available somewhere? |
@Prativa20 I was able to build the PR #40 myself. It looks promising. But it seems to no longer get the original name and ip_address under resource_configurations. It may be best to keep them for backward compatibility. Also, I haven't been able to figure out how to get the list of MachineName or ip_address from resources. What is the magic to make that happen? @diogoferreirasky To use a list in a resource such as |
@diogoferreirasky The latest release of vRealize Automation includes #30, and you can read the ip address from the network info, something like |
@diogoferreirasky @GMZwinge I tried adding all the data in the existing "resource_configuration" schema itself. This is also a solution for the issue #39 where currently the provider does not show all the VMs if _cluster > 1. In the following, my config file had _cluster = 2. So, that creates 2 VMs (Terraform-B0006 and Terraform-B0007) and the resource_configuration now shows information about both the VMs. "resource_configuration": { |
@Prativa20 I can try it when the changes are pushed to GitHub. What I am not sure is similar to the original #40: how to get the list of ip_address or MachineName from the above. Would something like this work: |
@Prativa20 do you have any idea when this might be finished and released? |
1. Addressing the following issues: https://github.com/terraform-providers/terraform-provider-vra7/issues/47 https://github.com/terraform-providers/terraform-provider-vra7/issues/43 https://github.com/terraform-providers/terraform-provider-vra7/issues/41 https://github.com/terraform-providers/terraform-provider-vra7/issues/39 https://github.com/terraform-providers/terraform-provider-vra7/issues/38 https://github.com/terraform-providers/terraform-provider-vra7/issues/33 https://github.com/terraform-providers/terraform-provider-vra7/issues/29 https://github.com/terraform-providers/terraform-provider-vra7/issues/27 https://github.com/terraform-providers/terraform-provider-vra7/issues/16 2. Re-designed the resource_configuration schema to include more properties 3. Implemented Day 2 operations for Scale In and Scale Out 4. Added import functionality 5. Updated the create and update logic as per the new schema 6. Modify read deployment to read all the properties retuned from the API 7. Added examples and documentation for the new schema Signed-off-by: Prativa Bawri <[email protected]>
1. Addressing the following issues: https://github.com/terraform-providers/terraform-provider-vra7/issues/47 https://github.com/terraform-providers/terraform-provider-vra7/issues/43 https://github.com/terraform-providers/terraform-provider-vra7/issues/41 https://github.com/terraform-providers/terraform-provider-vra7/issues/39 https://github.com/terraform-providers/terraform-provider-vra7/issues/38 https://github.com/terraform-providers/terraform-provider-vra7/issues/33 https://github.com/terraform-providers/terraform-provider-vra7/issues/29 https://github.com/terraform-providers/terraform-provider-vra7/issues/27 https://github.com/terraform-providers/terraform-provider-vra7/issues/16 2. Re-designed the resource_configuration schema to include more properties 3. Implemented Day 2 operations for Scale In and Scale Out 4. Added import functionality 5. Updated the create and update logic as per the new schema 6. Modify read deployment to read all the properties retuned from the API 7. Added examples and documentation for the new schema Signed-off-by: Prativa Bawri <[email protected]>
1. Addressing the following issues: https://github.com/terraform-providers/terraform-provider-vra7/issues/47 https://github.com/terraform-providers/terraform-provider-vra7/issues/43 https://github.com/terraform-providers/terraform-provider-vra7/issues/41 https://github.com/terraform-providers/terraform-provider-vra7/issues/39 https://github.com/terraform-providers/terraform-provider-vra7/issues/38 https://github.com/terraform-providers/terraform-provider-vra7/issues/33 https://github.com/terraform-providers/terraform-provider-vra7/issues/29 https://github.com/terraform-providers/terraform-provider-vra7/issues/27 https://github.com/terraform-providers/terraform-provider-vra7/issues/16 2. Re-designed the resource_configuration schema to include more properties 3. Implemented Day 2 operations for Scale In and Scale Out 4. Added import functionality 5. Updated the create and update logic as per the new schema 6. Modify read deployment to read all the properties retuned from the API 7. Added examples and documentation for the new schema Signed-off-by: Prativa Bawri <[email protected]>
1. Addressing the following issues: https://github.com/terraform-providers/terraform-provider-vra7/issues/47 https://github.com/terraform-providers/terraform-provider-vra7/issues/43 https://github.com/terraform-providers/terraform-provider-vra7/issues/41 https://github.com/terraform-providers/terraform-provider-vra7/issues/39 https://github.com/terraform-providers/terraform-provider-vra7/issues/38 https://github.com/terraform-providers/terraform-provider-vra7/issues/33 https://github.com/terraform-providers/terraform-provider-vra7/issues/29 https://github.com/terraform-providers/terraform-provider-vra7/issues/27 https://github.com/terraform-providers/terraform-provider-vra7/issues/16 2. Re-designed the resource_configuration schema to include more properties 3. Implemented Day 2 operations for Scale In and Scale Out 4. Added import functionality 5. Updated the create and update logic as per the new schema 6. Modify read deployment to read all the properties retuned from the API 7. Added examples and documentation for the new schema Signed-off-by: Prativa Bawri <[email protected]>
1. Addressing the following issues: https://github.com/terraform-providers/terraform-provider-vra7/issues/47 https://github.com/terraform-providers/terraform-provider-vra7/issues/43 https://github.com/terraform-providers/terraform-provider-vra7/issues/41 https://github.com/terraform-providers/terraform-provider-vra7/issues/39 https://github.com/terraform-providers/terraform-provider-vra7/issues/38 https://github.com/terraform-providers/terraform-provider-vra7/issues/33 https://github.com/terraform-providers/terraform-provider-vra7/issues/29 https://github.com/terraform-providers/terraform-provider-vra7/issues/27 https://github.com/terraform-providers/terraform-provider-vra7/issues/16 2. Re-designed the resource_configuration schema to include more properties 3. Implemented Day 2 operations for Scale In and Scale Out 4. Added import functionality 5. Updated the create and update logic as per the new schema 6. Modify read deployment to read all the properties retuned from the API 7. Added examples and documentation for the new schema Signed-off-by: Prativa Bawri <[email protected]>
1. Addressing the following issues: https://github.com/terraform-providers/terraform-provider-vra7/issues/55 https://github.com/terraform-providers/terraform-provider-vra7/issues/54 https://github.com/terraform-providers/terraform-provider-vra7/issues/47 https://github.com/terraform-providers/terraform-provider-vra7/issues/43 https://github.com/terraform-providers/terraform-provider-vra7/issues/41 https://github.com/terraform-providers/terraform-provider-vra7/issues/39 https://github.com/terraform-providers/terraform-provider-vra7/issues/38 https://github.com/terraform-providers/terraform-provider-vra7/issues/33 https://github.com/terraform-providers/terraform-provider-vra7/issues/29 https://github.com/terraform-providers/terraform-provider-vra7/issues/27 https://github.com/terraform-providers/terraform-provider-vra7/issues/16 2. Re-designed the resource_configuration schema to include more properties 3. Implemented Day 2 operations for Scale In and Scale Out and Change Lease 4. Added import functionality 5. Added vra7_deployment data source 6. Updated the create and update logic as per the new schema 7. Modify read deployment to read all the properties retuned from the API 8. Modified README.md, examples and documentation as per the new schema Signed-off-by: Prativa Bawri <[email protected]>
1. Addressing the following issues: https://github.com/terraform-providers/terraform-provider-vra7/issues/55 https://github.com/terraform-providers/terraform-provider-vra7/issues/54 https://github.com/terraform-providers/terraform-provider-vra7/issues/47 https://github.com/terraform-providers/terraform-provider-vra7/issues/43 https://github.com/terraform-providers/terraform-provider-vra7/issues/41 https://github.com/terraform-providers/terraform-provider-vra7/issues/39 https://github.com/terraform-providers/terraform-provider-vra7/issues/38 https://github.com/terraform-providers/terraform-provider-vra7/issues/33 https://github.com/terraform-providers/terraform-provider-vra7/issues/29 https://github.com/terraform-providers/terraform-provider-vra7/issues/27 https://github.com/terraform-providers/terraform-provider-vra7/issues/16 2. Re-designed the resource_configuration schema to include more properties 3. Implemented Day 2 operations for Scale In and Scale Out and Change Lease 4. Added import functionality 5. Added vra7_deployment data source 6. Updated the create and update logic as per the new schema 7. Modify read deployment to read all the properties retuned from the API 8. Modified README.md, examples and documentation as per the new schema Signed-off-by: Prativa Bawri <[email protected]>
1. Addressing the following issues: https://github.com/terraform-providers/terraform-provider-vra7/issues/55 https://github.com/terraform-providers/terraform-provider-vra7/issues/54 https://github.com/terraform-providers/terraform-provider-vra7/issues/47 https://github.com/terraform-providers/terraform-provider-vra7/issues/43 https://github.com/terraform-providers/terraform-provider-vra7/issues/41 https://github.com/terraform-providers/terraform-provider-vra7/issues/39 https://github.com/terraform-providers/terraform-provider-vra7/issues/38 https://github.com/terraform-providers/terraform-provider-vra7/issues/33 https://github.com/terraform-providers/terraform-provider-vra7/issues/29 https://github.com/terraform-providers/terraform-provider-vra7/issues/27 https://github.com/terraform-providers/terraform-provider-vra7/issues/16 2. Re-designed the resource_configuration schema to include more properties 3. Implemented Day 2 operations for Scale In and Scale Out and Change Lease 4. Added import functionality 5. Added vra7_deployment data source 6. Updated the create and update logic as per the new schema 7. Modify read deployment to read all the properties retuned from the API 8. Modified README.md, examples and documentation as per the new schema Signed-off-by: Prativa Bawri <[email protected]>
1. Addressing the following issues: https://github.com/terraform-providers/terraform-provider-vra7/issues/55 https://github.com/terraform-providers/terraform-provider-vra7/issues/54 https://github.com/terraform-providers/terraform-provider-vra7/issues/47 https://github.com/terraform-providers/terraform-provider-vra7/issues/43 https://github.com/terraform-providers/terraform-provider-vra7/issues/41 https://github.com/terraform-providers/terraform-provider-vra7/issues/39 https://github.com/terraform-providers/terraform-provider-vra7/issues/38 https://github.com/terraform-providers/terraform-provider-vra7/issues/33 https://github.com/terraform-providers/terraform-provider-vra7/issues/29 https://github.com/terraform-providers/terraform-provider-vra7/issues/27 https://github.com/terraform-providers/terraform-provider-vra7/issues/16 2. Re-designed the resource_configuration schema to include more properties 3. Implemented Day 2 operations for Scale In and Scale Out and Change Lease 4. Added import functionality 5. Added vra7_deployment data source 6. Updated the create and update logic as per the new schema 7. Modify read deployment to read all the properties retuned from the API 8. Modified README.md, examples and documentation as per the new schema Signed-off-by: Prativa Bawri <[email protected]>
1. Addressing the following issues: https://github.com/terraform-providers/terraform-provider-vra7/issues/55 https://github.com/terraform-providers/terraform-provider-vra7/issues/54 https://github.com/terraform-providers/terraform-provider-vra7/issues/47 https://github.com/terraform-providers/terraform-provider-vra7/issues/43 https://github.com/terraform-providers/terraform-provider-vra7/issues/41 https://github.com/terraform-providers/terraform-provider-vra7/issues/39 https://github.com/terraform-providers/terraform-provider-vra7/issues/38 https://github.com/terraform-providers/terraform-provider-vra7/issues/33 https://github.com/terraform-providers/terraform-provider-vra7/issues/29 https://github.com/terraform-providers/terraform-provider-vra7/issues/27 https://github.com/terraform-providers/terraform-provider-vra7/issues/16 2. Re-designed the resource_configuration schema to include more properties 3. Implemented Day 2 operations for Scale In and Scale Out and Change Lease 4. Added import functionality 5. Added vra7_deployment data source 6. Updated the create and update logic as per the new schema 7. Modify read deployment to read all the properties retuned from the API 8. Modified README.md, examples and documentation as per the new schema Signed-off-by: Prativa Bawri <[email protected]>
1. Addressing the following issues: https://github.com/terraform-providers/terraform-provider-vra7/issues/55 https://github.com/terraform-providers/terraform-provider-vra7/issues/54 https://github.com/terraform-providers/terraform-provider-vra7/issues/47 https://github.com/terraform-providers/terraform-provider-vra7/issues/43 https://github.com/terraform-providers/terraform-provider-vra7/issues/41 https://github.com/terraform-providers/terraform-provider-vra7/issues/39 https://github.com/terraform-providers/terraform-provider-vra7/issues/38 https://github.com/terraform-providers/terraform-provider-vra7/issues/33 https://github.com/terraform-providers/terraform-provider-vra7/issues/29 https://github.com/terraform-providers/terraform-provider-vra7/issues/27 https://github.com/terraform-providers/terraform-provider-vra7/issues/16 2. Re-designed the resource_configuration schema to include more properties 3. Implemented Day 2 operations for Scale In and Scale Out and Change Lease 4. Added import functionality 5. Added vra7_deployment data source 6. Updated the create and update logic as per the new schema 7. Modify read deployment to read all the properties retuned from the API 8. Modified README.md, examples and documentation as per the new schema Signed-off-by: Prativa Bawri <[email protected]>
1. Addressing the following issues: https://github.com/terraform-providers/terraform-provider-vra7/issues/55 https://github.com/terraform-providers/terraform-provider-vra7/issues/54 https://github.com/terraform-providers/terraform-provider-vra7/issues/47 https://github.com/terraform-providers/terraform-provider-vra7/issues/43 https://github.com/terraform-providers/terraform-provider-vra7/issues/41 https://github.com/terraform-providers/terraform-provider-vra7/issues/39 https://github.com/terraform-providers/terraform-provider-vra7/issues/38 https://github.com/terraform-providers/terraform-provider-vra7/issues/33 https://github.com/terraform-providers/terraform-provider-vra7/issues/29 https://github.com/terraform-providers/terraform-provider-vra7/issues/27 https://github.com/terraform-providers/terraform-provider-vra7/issues/16 2. Re-designed the resource_configuration schema to include more properties 3. Implemented Day 2 operations for Scale In and Scale Out and Change Lease 4. Added import functionality 5. Added vra7_deployment data source 6. Updated the create and update logic as per the new schema 7. Modify read deployment to read all the properties retuned from the API 8. Modified README.md, examples and documentation as per the new schema Signed-off-by: Prativa Bawri <[email protected]>
1. Addressing the following issues: https://github.com/terraform-providers/terraform-provider-vra7/issues/55 https://github.com/terraform-providers/terraform-provider-vra7/issues/54 https://github.com/terraform-providers/terraform-provider-vra7/issues/47 https://github.com/terraform-providers/terraform-provider-vra7/issues/43 https://github.com/terraform-providers/terraform-provider-vra7/issues/41 https://github.com/terraform-providers/terraform-provider-vra7/issues/39 https://github.com/terraform-providers/terraform-provider-vra7/issues/38 https://github.com/terraform-providers/terraform-provider-vra7/issues/33 https://github.com/terraform-providers/terraform-provider-vra7/issues/29 https://github.com/terraform-providers/terraform-provider-vra7/issues/27 https://github.com/terraform-providers/terraform-provider-vra7/issues/16 2. Re-designed the resource_configuration schema to include more properties 3. Implemented Day 2 operations for Scale In and Scale Out and Change Lease 4. Added import functionality 5. Added vra7_deployment data source 6. Updated the create and update logic as per the new schema 7. Modify read deployment to read all the properties retuned from the API 8. Modified README.md, examples and documentation as per the new schema Signed-off-by: Prativa Bawri <[email protected]>
@MaciejKaras @GMZwinge @diogoferreirasky #40 has been merged. The latest version, v1.0.0 has this change. Please refer to the README, documentation and examples for detail on migrating to this version. |
The current implementation provides very limited information about the deployment in the state file.
I have created a PR which will give a lot more information about the deployment returned from the API
#40
For instance, if the config file has the following information:
_deployment_configuration = {
"_leaseDays" = "15"
"BPCustomProperty" = "custom deployment property"
}
resource_configuration = {
"vSphere1.cpu" = 1
"vSphere1.memory" = 1024
"vSphere1.cluster" = 2
"vSphere1.vSphere1CustomProperty" = "machine custom property"
}
The CURRENT STATE file looks something like this:
resource_configuration = [
{
"vSphere1.cpu" = 1
"vSphere1.memory" = 1024
"vSphere1._cluster" = 2
"vSphere1.vSphere1CustomProperty" = "machine custom property"
},
]
The NEW STATE, will look like this. A new resources property is added in the schema:
"resources": [
{
"component_name": "",
"properties": {},
"id": "931a1a-cba6-4ec1-9aba-35db1886",
"name": "Terraform-Simple-BP-43325908",
"type": "composition.resource.type.deployment"
},
{
"component_name": "vSphere1",
"properties": {
"ChangeLease": "true",
"ChangeOwner": "true",
"Component": "vSphere1",
"ConnectViaNativeVmrc": "true",
"ConnectViaVmrc": "true",
"CreateSnapshot": "true",
"DISK_VOLUMES.0.DISK_CAPACITY": "8",
"DISK_VOLUMES.0.DISK_INPUT_ID": "DISK_INPUT_ID1",
"DISK_VOLUMES.0.DISK_LABEL": "Hard disk 1",
"DISK_VOLUMES.1.DISK_CAPACITY": "2",
"DISK_VOLUMES.1.DISK_INPUT_ID": "DISK_INPUT_ID2",
"Destroy": "true",
"EXTERNAL_REFERENCE_ID": "vm-26",
"Expire": "true",
"IS_COMPONENT_MACHINE": "false",
"InstallTools": "true",
"MachineBlueprintName": "Terraform-Simple-BP",
"MachineCPU": "1",
"MachineDailyCost": "0",
"MachineDestructionDate": "2020-03-17T22:49:10.620Z",
"MachineExpirationDate": "2019-12-18T22:49:10.620Z",
"MachineGroupName": "Terraform-BG",
"MachineGuestOperatingSystem": "CentOS 4/5/6/7 (64-bit)",
"MachineInterfaceDisplayName": "vSphere (vCenter)",
"MachineInterfaceType": "vSphere",
"MachineMemory": "1024",
"MachineName": "Terraform-B05",
"MachineReservationName": "Terraform-reservation",
"MachineStorage": "10",
"MachineType": "Virtual",
"NETWORK_LIST.0.NETWORK_MAC_ADDRESS": "00:55:56:c6:63:6a",
"NETWORK_LIST.0.NETWORK_NAME": "dvPort-vm-1521",
"PowerOff": "true",
"Reboot": "true",
"Reconfigure": "true",
"Relocate": "true",
"Reprovision": "true",
"Reset": "true",
"Shutdown": "true",
"Suspend": "true",
"Unregister": "true",
"VirtualMachine.Admin.UUID": "502-0221-ca38-c6de-aae1d831b",
"endpointExternalReferenceId": "827cd6-9fd7-4477-bd2f-b637",
"ip_address": "20.115.100.20",
"machineId": "a11c8a-e275-4a27-b3d9-b889db1"
},
"id": "d833-fe02-4a97-8cb5-acb1b6f5",
"name": "Terraform-B0",
"type": "Infrastructure.Virtual"
},
{
"component_name": "vSphere1",
"properties": {
"ChangeLease": "true",
"ChangeOwner": "true",
"Component": "vSphere1",
"ConnectViaNativeVmrc": "true",
"ConnectViaVmrc": "true",
"CreateSnapshot": "true",
"DISK_VOLUMES.0.DISK_CAPACITY": "8",
"DISK_VOLUMES.0.DISK_INPUT_ID": "DISK_INPUT_ID1",
"DISK_VOLUMES.0.DISK_LABEL": "Hard disk 1",
"DISK_VOLUMES.1.DISK_CAPACITY": "2",
"DISK_VOLUMES.1.DISK_INPUT_ID": "DISK_INPUT_ID2",
"Destroy": "true",
"EXTERNAL_REFERENCE_ID": "vm-127",
"Expire": "true",
"IS_COMPONENT_MACHINE": "false",
"InstallTools": "true",
"MachineBlueprintName": "Terraform-Simple-BP",
"MachineCPU": "1",
"MachineDailyCost": "0",
"MachineDestructionDate": "2020-03-17T22:49:07.323Z",
"MachineExpirationDate": "2019-12-18T22:49:07.323Z",
"MachineGroupName": "Terraform-BG",
"MachineGuestOperatingSystem": "CentOS 4/5/6/7 (64-bit)",
"MachineInterfaceDisplayName": "vSphere (vCenter)",
"MachineInterfaceType": "vSphere",
"MachineMemory": "1024",
"MachineName": "Terraform-B04",
"MachineReservationName": "Terraform-reservation",
"MachineStorage": "10",
"MachineType": "Virtual",
"NETWORK_LIST.0.NETWORK_MAC_ADDRESS": "00:a0:56:b4:2a:4c",
"NETWORK_LIST.0.NETWORK_NAME": "Grp-wdc-m-vm-1521",
"PowerOff": "true",
"Reboot": "true",
"Reconfigure": "true",
"Relocate": "true",
"Reprovision": "true",
"Reset": "true",
"Shutdown": "true",
"Suspend": "true",
"Unregister": "true",
"VirtualMachine.Admin.UUID": "50d6-d760-f701-4f1f-831658d",
"endpointExternalReferenceId": "8ddd6-9fd7-4477-bd2f-84337",
"ip_address": "10.145.155.145",
"machineId": "b3b747-3852-4af1-bc96-cf71d"
},
"id": "24dcc989-7b4f-49bf-905e9239b2",
"name": "Terraform-B0004",
"type": "Infrastructure.Virtual"
}
]
I would appreciate any feedback on this.
@markpeek @cars @mcascone @GMZwinge @hobovirtual @diogoferreirasky
The text was updated successfully, but these errors were encountered: