Modules on CloudBolt Documentation

Templating and Property Toolkit

Mon, 01 Jan 0001 00:00:00 +0000

To learn more about this OneFuse feature, refer to Templating guide and Property Toolkit features.

Introduction

The OneFuse Property Toolkit (PTK) is the Swiss army knife of the OneFuse Platform.

PTK can be used to simplify configurations, define business logic as configuration, build simple logic or tackle the most complex problems. At face value, the PTK is meta-data that can be called upon offering simple name value pairs that can be used as a reference for decision making. In its most powerful form, it can contain logic, decision trees, platform abstractions, and much more.

Ansible Tower

Mon, 01 Jan 0001 00:00:00 +0000

To learn more about this OneFuse module, refer to Ansible Tower.

Prerequisites

Configure the OneFuse Provider
Review an overview on OneFuse Modules with Terraform

Steps

Create variables.tf file
Create main.tf file
Run terraform commands to deploy a OneFuse Ansible Tower Deployment and run Provision Job Template(s):
1. terraform init
2. terraform plan
3. terraform apply
Run terraform command to destroy OneFuse Ansible Tower Deployment and run Deprovision Job Template(s), if any:
- terraform destroy

Create variables.tf

Add the following in the variables.tf file. Update the values as needed.

DNS

Mon, 01 Jan 0001 00:00:00 +0000

To learn more about this OneFuse module, refer to DNS.

Prerequisites

Configure the OneFuse Provider
Review an overview on OneFuse Modules with Terraform

Steps

Create variables.tf file
Create main.tf file
Run terraform commands to register DNS Record(s):
1. terraform init
2. terraform plan
3. terraform apply
Run terraform command to release the DNS Record(s):
- terraform destroy

Create variables.tf

Add the following in the variables.tf file. Update the values as needed.

It is a best practice to separate configurations into identifiable files, refer to Best practices for OneFuse modules.

The sample below shows all configurations in one variables.tf file for simplicity.

IPAM

Mon, 01 Jan 0001 00:00:00 +0000

To learn more about this OneFuse module, refer to IPAM.

Prerequisites

Configure the OneFuse Provider
Review an overview on OneFuse Modules with Terraform

Steps

Create variables.tf file
Create main.tf file
Run terraform commands to reserve an IP Address:
1. terraform init
2. terraform plan
3. terraform apply
Run terraform command to release the IP Address:
- terraform destroy

Create variables.tf

Add the following in the variables.tf file. Update the values as needed.

It is a best practice to separate configurations into identifiable files, refer to Best practices for OneFuse modules.

The sample below shows all configurations in one variables.tf file for simplicity.

Microsoft Active Directory

Mon, 01 Jan 0001 00:00:00 +0000

To learn more about this OneFuse module, refer to Microsoft Active Directory.

Prerequisites

Configure the OneFuse Provider
Review an overview on OneFuse Modules with Terraform

Steps

Create variables.tf file
Create main.tf file
Run terraform commands to create a Computer Account in AD:
1. terraform init
2. terraform plan
3. terraform apply
Run terraform command to delete the Computer Account from AD:
- terraform destroy

Create variables.tf

Add the following in the variables.tf file. Update the values as needed.

Naming

Mon, 01 Jan 0001 00:00:00 +0000

To learn more about this OneFuse module, refer to Naming.

Prerequisites

Configure the OneFuse Provider
Review an overview on OneFuse Modules with Terraform

Steps

Create variables.tf file
Create main.tf file

Run terraform commands to generate a Name:

terraform init
terraform plan
terraform apply

Example apply output:

$ terraform init

Initializing the backend...

Initializing provider plugins...

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

$ terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.


------------------------------------------------------------------------

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # onefuse_naming.my_name will be created
  + resource "onefuse_naming" "my_name" {
      + custom_name_id      = (known after apply)
      + dns_suffix          = "company.com"
      + id                  = (known after apply)
      + name                = (known after apply)
      + naming_policy_id    = "2"
      + template_properties = {
          + "Application" = "Web Servers"
          + "env"         = "prod"
          + "location"    = "atl"
          + "os"          = "linux"
          + "suffix"      = "company.com"
    }

Plan: 1 to add, 0 to change, 0 to destroy.

------------------------------------------------------------------------

Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.

$ terraform apply

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # onefuse_naming.my_name will be created
  + resource "onefuse_naming" "my_name" {
      + custom_name_id      = (known after apply)
      + dns_suffix          = "company.com"
      + id                  = (known after apply)
      + name                = (known after apply)
      + naming_policy_id    = "2"
      + template_properties = {
          + "Application" = "Web Servers"
          + "env"         = "prod"
          + "location"    = "atl"
          + "os"          = "linux"
          + "suffix"      = "company.com"
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

onefuse_naming.my_name: Creating...
onefuse_naming.my_name: Creation complete after 1s [id=prodlinuxatl2.company.com]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

$ terraform show
# onefuse_naming.my_name:
resource "onefuse_naming" "my_name" {
    custom_name_id      = 31
    dns_suffix          = "company.com"
    id                  = "prodlinuxatl2.company.com"
    name                = "prodlinuxatl2"
    naming_policy_id    = "2"
    template_properties = {
        "Application" = "Web Servers"
        "env"         = "prod"
        "location"    = "atl"
        "os"          = "linux"
        "suffix"      = "company.com"
    }
}

Run terraform command to destroy a generated Name:

terraform destroy

Example destroy output:

$ terraform destroy
onefuse_naming.my_name: Refreshing state... [id=prodlinuxatl2.company.com]

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  - destroy

Terraform will perform the following actions:

  # onefuse_naming.my_name will be destroyed
  - resource "onefuse_naming" "my_name" {
      - custom_name_id      = 31 -> null
      - dns_suffix          = "company.com" -> null
      - id                  = "prodlinuxatl2.company.com" -> null
      - name                = "prodlinuxatl2" -> null
      - naming_policy_id    = "2" -> null
      - template_properties = {
          - "Application" = "Web Servers"
          - "env"         = "prod"
          - "location"    = "atl"
          - "os"          = "linux"
          - "suffix"      = "company.com"
        } -> null
    }

Plan: 0 to add, 0 to change, 1 to destroy.

Do you really want to destroy all resources?
  Terraform will destroy all your managed infrastructure, as shown above.
  There is no undo. Only 'yes' will be accepted to confirm.

  Enter a value: yes

onefuse_naming.my_name: Destroying... [id=prodlinuxatl2.company.com]
onefuse_naming.my_name: Destruction complete after 0s

Destroy complete! Resources: 1 destroyed.
$ terraform show

$

Pluggable modules

Mon, 01 Jan 0001 00:00:00 +0000

To learn more about this OneFuse module, refer to Pluggable modules.

Prerequisites

Configure the OneFuse Provider
Review an overview on OneFuse Modules with Terraform

Steps

Create variables.tf file
Create main.tf file
Run terraform commands to deploy a OneFuse Pluggable Module Deployment and run provisioning scenario(s):
1. terraform init
2. terraform plan
3. terraform apply
Run terraform command to destroy OneFuse Pluggable Module Deployment and run deprovision scenario(s), if any:
- terraform destroy

Create variables.tf

Add the following in the variables.tf file. Update the values as needed.

Scripting

Mon, 01 Jan 0001 00:00:00 +0000

To learn more about the Scripting module in OneFuse, refer to Scripting.

Prerequisites

Configure the OneFuse Provider
Review an overview on OneFuse Modules with Terraform

Steps

Create variables.tf file
Create main.tf file
Run terraform commands to deploy a OneFuse Scripting Deployment and run the Provision Script:
1. terraform init
2. terraform plan
3. terraform apply
Run terraform command to destroy the OneFuse Scripting Deployment and run the Deprovision Script:
- terraform destroy

Create variables.tf

Add the following in the variables.tf file. Update the values as needed.

ServiceNow CMDB

Mon, 01 Jan 0001 00:00:00 +0000

To learn more about this OneFuse module, refer to ServiceNow CMDB.

Prerequisites

Configure the OneFuse Provider
Review an overview on OneFuse Modules with Terraform

Steps

Create variables.tf file
Create main.tf file

Run terraform commands to create a ServiceNow CI:

terraform init
terraform plan
terraform apply

See example apply output:

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # onefuse_servicenow_cmdb_deployment.my_servicenow_cmdb_deployment will be created
  + resource "onefuse_servicenow_cmdb_deployment" "my_servicenow_cmdb_deployment" {
      + configuration_items_info = (known after apply)
      + id                       = (known after apply)
      + policy_id                = 72
      + template_properties      = {
          + "OneFuse_Suffix" = "company.com"
          + "cpuCount"       = "2"
          + "dnsSuffix"      = "company.com"
          + "fqdn"           = "myhost.company.com"
          + "hostname"       = "myhost"
          + "ipAddress"      = "10.10.2.7"
          + "memoryMB"       = "4"
          + "platformUuid"   = "634f89cd-bcf8-421b-bfa3-65f09557abca"
          + "powerState"     = "On"
          + "totalStorageGB" = "30"
        }
      + workspace_url            = (known after apply)
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Changes to Outputs:
  + servicenow-cmdb-response = (known after apply)

------------------------------------------------------------------------

Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.


An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # onefuse_servicenow_cmdb_deployment.my_servicenow_cmdb_deployment will be created
  + resource "onefuse_servicenow_cmdb_deployment" "my_servicenow_cmdb_deployment" {
      + configuration_items_info = (known after apply)
      + id                       = (known after apply)
      + policy_id                = 72
      + template_properties      = {
          + "OneFuse_Suffix" = "company.com"
          + "cpuCount"       = "2"
          + "dnsSuffix"      = "company.com"
          + "fqdn"           = "myhost.company.com"
          + "hostname"       = "myhost"
          + "ipAddress"      = "10.10.2.7"
          + "memoryMB"       = "4"
          + "platformUuid"   = "634f89cd-bcf8-421b-bfa3-65f09557abca"
          + "powerState"     = "On"
          + "totalStorageGB" = "30"
        }
      + workspace_url            = (known after apply)
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Changes to Outputs:
  + servicenow-cmdb-response = (known after apply)

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

onefuse_servicenow_cmdb_deployment.my_servicenow_cmdb_deployment: Creating...
onefuse_servicenow_cmdb_deployment.my_servicenow_cmdb_deployment: Still creating... [10s elapsed]
onefuse_servicenow_cmdb_deployment.my_servicenow_cmdb_deployment: Creation complete after 14s [id=73]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

Outputs:

servicenow-cmdb-response = tolist([
  tomap({
    "ciClassName" = "cmdb_ci_linux_server"
    "ciName" = "myhost-company.com"
  }),
])

Modify values, then run terraform apply again to update the ServiceNow CI:

In our example below, the cpuCount was updated from 2 to 4.

See example apply output:

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # onefuse_servicenow_cmdb_deployment.my_servicenow_cmdb_deployment will be updated in-place
  ~ resource "onefuse_servicenow_cmdb_deployment" "my_servicenow_cmdb_deployment" {
        id                       = "73"
      ~ template_properties      = {
          ~ "cpuCount"       = "2" -> "4"
            # (9 unchanged elements hidden)
        }
        # (3 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

onefuse_servicenow_cmdb_deployment.my_servicenow_cmdb_deployment: Modifying... [id=73]
onefuse_servicenow_cmdb_deployment.my_servicenow_cmdb_deployment: Still modifying... [id=73, 10s elapsed]
onefuse_servicenow_cmdb_deployment.my_servicenow_cmdb_deployment: Modifications complete after 13s [id=73]

Apply complete! Resources: 0 added, 1 changed, 0 destroyed.

Outputs:

servicenow-cmdb-response = tolist([
  tomap({
    "ciClassName" = "cmdb_ci_linux_server"
    "ciName" = "myhost-company.com"
  }),
])

Run terraform command to delete the ServiceNow CI:

terraform destroy

See example destroy output:

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  - destroy

Terraform will perform the following actions:

  # onefuse_servicenow_cmdb_deployment.my_servicenow_cmdb_deployment will be destroyed
  - resource "onefuse_servicenow_cmdb_deployment" "my_servicenow_cmdb_deployment" {
      - configuration_items_info = [
          - {
              - "ciClassName" = "cmdb_ci_linux_server"
              - "ciName"      = "myhost-company.com"
            },
        ] -> null
      - id                       = "73" -> null
      - policy_id                = 72 -> null
      - template_properties      = {
          - "OneFuse_Suffix" = "company.com"
          - "cpuCount"       = "4"
          - "dnsSuffix"      = "company.com"
          - "fqdn"           = "myhost.company.com"
          - "hostname"       = "myhost"
          - "ipAddress"      = "10.10.2.7"
          - "memoryMB"       = "4"
          - "platformUuid"   = "634f89cd-bcf8-421b-bfa3-65f09557abca"
          - "powerState"     = "On"
          - "totalStorageGB" = "30"
        } -> null
      - workspace_url            = "/api/v3/onefuse/workspaces/2/" -> null
    }

Plan: 0 to add, 0 to change, 1 to destroy.

Changes to Outputs:
  - servicenow-cmdb-response = [
      - {
          - "ciClassName" = "cmdb_ci_linux_server"
          - "ciName"      = "myhost-company.com"
        },
    ] -> null

Do you really want to destroy all resources?
  Terraform will destroy all your managed infrastructure, as shown above.
  There is no undo. Only 'yes' will be accepted to confirm.

  Enter a value: yes

onefuse_servicenow_cmdb_deployment.my_servicenow_cmdb_deployment: Destroying... [id=73]
onefuse_servicenow_cmdb_deployment.my_servicenow_cmdb_deployment: Still destroying... [id=73, 10s elapsed]
onefuse_servicenow_cmdb_deployment.my_servicenow_cmdb_deployment: Destruction complete after 12s

Destroy complete! Resources: 1 destroyed.

VMware Aria Automation

Mon, 01 Jan 0001 00:00:00 +0000

To learn more about this OneFuse Module, refer to Aria Automation.

Prerequisites

Configure the OneFuse Provider
Review an overview on OneFuse Modules with Terraform

Steps

Create variables.tf file
Create main.tf file

Run terraform commands to deploy a VMware Aria Automation Deployment:

terraform init
terraform plan
terraform apply

Example apply output:

Initializing the backend...

Initializing provider plugins...
- Reusing previous version of cloudboltsoftware/onefuse from the dependency lock file
- Using previously-installed cloudboltsoftware/onefuse v1.20.0

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # onefuse_vra_deployment.my_vra_deployment will be created
  + resource "onefuse_vra_deployment" "my_vra_deployment" {
      + blueprint_name      = (known after apply)
      + deployment_info     = (known after apply)
      + deployment_name     = "tf_vra_deployment"
      + id                  = (known after apply)
      + policy_id           = 1
      + project_name        = (known after apply)
      + template_properties = {
          + "Environment" = "Dev"
        }
      + workspace_url       = (known after apply)
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Changes to Outputs:
  + deployment_info = (known after apply)

------------------------------------------------------------------------

Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.


An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # onefuse_vra_deployment.my_vra_deployment will be created
  + resource "onefuse_vra_deployment" "my_vra_deployment" {
      + blueprint_name      = (known after apply)
      + deployment_info     = (known after apply)
      + deployment_name     = "tf_vra_deployment"
      + id                  = (known after apply)
      + policy_id           = 1
      + project_name        = (known after apply)
      + template_properties = {
          + "Environment" = "Dev"
        }
      + workspace_url       = (known after apply)
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Changes to Outputs:
  + deployment_info = (known after apply)

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

onefuse_vra_deployment.my_vra_deployment: Creating...
onefuse_vra_deployment.my_vra_deployment: Still creating... [10s elapsed]
...
onefuse_vra_deployment.my_vra_deployment: Creation complete after 21m9s [id=1]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

Outputs:

deployment_info = "{\"blueprintId\":\"30adbde1-914b-48ae-80d5-38f67a0a76fd\",\"blueprintVersion\":\"1\",\"childResources\":[{\"createdAt\":\"2021-04-07T20:12:59.012526Z\",\"id\":\"89a59c4d-b64f-407f-a393-fe391c9023d5\",\"name\":\"Cloud_vSphere_Machine_1\",\"properties\":{\"account\":\"vcenter.company.com\",\"componentType\":\"Cloud.vSphere.Machine\",\"computeHostRef\":\"ResourcePool:resgroup-223319\",\"computeHostType\":\"ResourcePool\",\"coreCount\":\"1\",\"cpuCount\":1,\"datastoreName\":\"XtremIO\",\"endpointId\":\"0cf54d7c-f889-42b2-9596-275723a4442b\",\"endpointType\":\"vsphere\",\"flavorMappingName\":\"\",\"id\":\"/resources/compute/89a59c4d-b64f-407f-a393-fe391c9023d5\",\"imageRef\":\"MassTesting\",\"name\":\"Cloud_vSphere_Machine_1\",\"networks\":[{\"assignment\":\"dynamic\",\"deviceIndex\":0,\"id\":\"/resources/network-interfaces/184557fe-7a0f-4eff-94c4-87dd4e5df2f1\",\"mac_address\":\"00:50:56:a5:10:ac\",\"name\":\"dvs_102_10.10.2.0_24\",\"resourceName\":\"dvs_102_10.10.2.0_24\"}],\"osType\":\"LINUX\",\"powerState\":\"ON\",\"primaryMAC\":\"00:50:56:a5:10:ac\",\"project\":\"ae8d2e8e-ace6-4bf2-916a-bb10aa731d1b\",\"providerId\":\"5025e14b-38b7-8ea0-ce5b-580eb8bee60d\",\"provisionGB\":\"0\",\"region\":\"onefuse\",\"resourceDescLink\":\"/resources/compute-descriptions/efd6c152-6bab-4a78-af9f-079743f09cbb\",\"resourceId\":\"89a59c4d-b64f-407f-a393-fe391c9023d5\",\"resourceLink\":\"/resources/compute/89a59c4d-b64f-407f-a393-fe391c9023d5\",\"resourceName\":\"vrauserqa-976\",\"resourcePool\":\"/resources/pools/7248f32e8f9b5c75-7f703c5265a63d87\",\"softwareName\":\"Other (64-bit)\",\"storage\":{\"disks\":[{\"bootOrder\":1,\"capacityGb\":0,\"controllerKey\":\"1000\",\"controllerUnitNumber\":\"0\",\"diskPlacementRef\":\"StoragePod:group-p100\",\"encrypted\":false,\"independent\":\"false\",\"name\":\"vrauserqa-976-boot-disk\",\"persistent\":false,\"provisionGB\":\"0\",\"provisioningType\":\"thin\",\"type\":\"HDD\",\"vcUuid\":\"634f89cd-bcf8-421b-bfa3-65f09557abca\",\"vm\":\"VirtualMachine:vm-710951\"}]},\"totalMemoryMB\":1024,\"vcUuid\":\"634f89cd-bcf8-421b-bfa3-65f09557abca\",\"zone\":\"Cluster1 / ESX Agents\",\"zone_overlapping_migrated\":\"true\"},\"state\":\"OK\",\"type\":\"Cloud.vSphere.Machine\"}],\"createdAt\":\"2021-04-07T20:12:42.249541Z\",\"createdBy\":\"vrauser\",\"description\":\"\",\"id\":\"6162920c-d7df-4018-b843-0bb5e68873b7\",\"inputs\":{\"cpuCount\":1,\"totalMemoryMB\":1024},\"lastUpdatedAt\":\"2021-04-07T20:33:29.905193Z\",\"lastUpdatedBy\":\"vrauser\",\"name\":\"tf_vra_deployment\",\"orgId\":\"c1cb7d03-37ee-4fbe-a052-6d2c4af5a8a8\",\"ownedBy\":\"vrauser\",\"projectId\":\"ae8d2e8e-ace6-4bf2-916a-bb10aa731d1b\",\"status\":\"CREATE_SUCCESSFUL\"}"

Run terraform command to destroy Aria Automation Deployment:

terraform destroy

Example destroy output:

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  - destroy

Terraform will perform the following actions:

  # onefuse_vra_deployment.my_vra_deployment will be destroyed
  - resource "onefuse_vra_deployment" "my_vra_deployment" {
      - blueprint_name      = "myblueprint" -> null
      - deployment_info     = jsonencode(
            {
              - blueprintId      = "30adbde1-914b-48ae-80d5-38f67a0a76fd"
              - blueprintVersion = "1"
              - childResources   = [
                  - {
                      - createdAt  = "2021-04-07T20:12:59.012526Z"
                      - id         = "89a59c4d-b64f-407f-a393-fe391c9023d5"
                      - name       = "Cloud_vSphere_Machine_1"
                      - properties = {
                          - account                   = "vcenter01.company.com"
                          - componentType             = "Cloud.vSphere.Machine"
                          - computeHostRef            = "ResourcePool:resgroup-223319"
                          - computeHostType           = "ResourcePool"
                          - coreCount                 = "1"
                          - cpuCount                  = 1
                          - datastoreName             = "XtremIO_5t_datastore3"
                          - endpointId                = "0cf54d7c-f889-42b2-9596-275723a4442b"
                          - endpointType              = "vsphere"
                          - flavorMappingName         = ""
                          - id                        = "/resources/compute/89a59c4d-b64f-407f-a393-fe391c9023d5"
                          - imageRef                  = "MassTesting"
                          - name                      = "Cloud_vSphere_Machine_1"
                          - networks                  = [
                              - {
                                  - assignment   = "dynamic"
                                  - deviceIndex  = 0
                                  - id           = "/resources/network-interfaces/184557fe-7a0f-4eff-94c4-87dd4e5df2f1"
                                  - mac_address  = "00:50:56:a5:10:ac"
                                  - name         = "dvs_102_10.10.2.0_24"
                                  - resourceName = "dvs_102_10.10.2.0_24"
                                },
                            ]
                          - osType                    = "LINUX"
                          - powerState                = "ON"
                          - primaryMAC                = "00:50:56:a5:10:ac"
                          - project                   = "ae8d2e8e-ace6-4bf2-916a-bb10aa731d1b"
                          - providerId                = "5025e14b-38b7-8ea0-ce5b-580eb8bee60d"
                          - provisionGB               = "0"
                          - region                    = "onefuse"
                          - resourceDescLink          = "/resources/compute-descriptions/efd6c152-6bab-4a78-af9f-079743f09cbb"
                          - resourceId                = "89a59c4d-b64f-407f-a393-fe391c9023d5"
                          - resourceLink              = "/resources/compute/89a59c4d-b64f-407f-a393-fe391c9023d5"
                          - resourceName              = "vrauserqa-976"
                          - resourcePool              = "/resources/pools/7248f32e8f9b5c75-7f703c5265a63d87"
                          - softwareName              = "Other (64-bit)"
                          - storage                   = {
                              - disks = [
                                  - {
                                      - bootOrder            = 1
                                      - capacityGb           = 0
                                      - controllerKey        = "1000"
                                      - controllerUnitNumber = "0"
                                      - diskPlacementRef     = "StoragePod:group-p100"
                                      - encrypted            = false
                                      - independent          = "false"
                                      - name                 = "vrauserqa-976-boot-disk"
                                      - persistent           = false
                                      - provisionGB          = "0"
                                      - provisioningType     = "thin"
                                      - type                 = "HDD"
                                      - vcUuid               = "634f89cd-bcf8-421b-bfa3-65f09557abca"
                                      - vm                   = "VirtualMachine:vm-710951"
                                    },
                                ]
                            }
                          - totalMemoryMB             = 1024
                          - vcUuid                    = "634f89cd-bcf8-421b-bfa3-65f09557abca"
                          - zone                      = "Cluster1 / ESX Agents"
                          - zone_overlapping_migrated = "true"
                        }
                      - state      = "OK"
                      - type       = "Cloud.vSphere.Machine"
                    },
                ]
              - createdAt        = "2021-04-07T20:12:42.249541Z"
              - createdBy        = "vrauser"
              - description      = ""
              - id               = "6162920c-d7df-4018-b843-0bb5e68873b7"
              - inputs           = {
                  - cpuCount      = 1
                  - totalMemoryMB = 1024
                }
              - lastUpdatedAt    = "2021-04-07T20:33:29.905193Z"
              - lastUpdatedBy    = "vrauser"
              - name             = "tf_vra_deployment"
              - orgId            = "c1cb7d03-37ee-4fbe-a052-6d2c4af5a8a8"
              - ownedBy          = "vrauser"
              - projectId        = "ae8d2e8e-ace6-4bf2-916a-bb10aa731d1b"
              - status           = "CREATE_SUCCESSFUL"
            }
        ) -> null
      - deployment_name     = "tf_vra_deployment" -> null
      - id                  = "1" -> null
      - policy_id           = 1 -> null
      - project_name        = "Quickstart Project 1" -> null
      - template_properties = {
          - "Environment" = "Dev"
        } -> null
      - workspace_url       = "/api/v3/onefuse/workspaces/2/" -> null
    }

Plan: 0 to add, 0 to change, 1 to destroy.

Changes to Outputs:
  - deployment_info = jsonencode(
        {
          - blueprintId      = "30adbde1-914b-48ae-80d5-38f67a0a76fd"
          - blueprintVersion = "1"
          - childResources   = [
              - {
                  - createdAt  = "2021-04-07T20:12:59.012526Z"
                  - id         = "89a59c4d-b64f-407f-a393-fe391c9023d5"
                  - name       = "Cloud_vSphere_Machine_1"
                  - properties = {
                      - account                   = "vcenter01.company.com"
                      - componentType             = "Cloud.vSphere.Machine"
                      - computeHostRef            = "ResourcePool:resgroup-223319"
                      - computeHostType           = "ResourcePool"
                      - coreCount                 = "1"
                      - cpuCount                  = 1
                      - datastoreName             = "XtremIO_datastore3"
                      - endpointId                = "0cf54d7c-f889-42b2-9596-275723a4442b"
                      - endpointType              = "vsphere"
                      - flavorMappingName         = ""
                      - id                        = "/resources/compute/89a59c4d-b64f-407f-a393-fe391c9023d5"
                      - imageRef                  = "MassTesting"
                      - name                      = "Cloud_vSphere_Machine_1"
                      - networks                  = [
                          - {
                              - assignment   = "dynamic"
                              - deviceIndex  = 0
                              - id           = "/resources/network-interfaces/184557fe-7a0f-4eff-94c4-87dd4e5df2f1"
                              - mac_address  = "00:50:56:a5:10:ac"
                              - name         = "dvs_102_10.10.2.0_24"
                              - resourceName = "dvs_102_10.10.2.0_24"
                            },
                        ]
                      - osType                    = "LINUX"
                      - powerState                = "ON"
                      - primaryMAC                = "00:50:56:a5:10:ac"
                      - project                   = "ae8d2e8e-ace6-4bf2-916a-bb10aa731d1b"
                      - providerId                = "5025e14b-38b7-8ea0-ce5b-580eb8bee60d"
                      - provisionGB               = "0"
                      - region                    = "onefuse"
                      - resourceDescLink          = "/resources/compute-descriptions/efd6c152-6bab-4a78-af9f-079743f09cbb"
                      - resourceId                = "89a59c4d-b64f-407f-a393-fe391c9023d5"
                      - resourceLink              = "/resources/compute/89a59c4d-b64f-407f-a393-fe391c9023d5"
                      - resourceName              = "vrauserqa-976"
                      - resourcePool              = "/resources/pools/7248f32e8f9b5c75-7f703c5265a63d87"
                      - softwareName              = "Other (64-bit)"
                      - storage                   = {
                          - disks = [
                              - {
                                  - bootOrder            = 1
                                  - capacityGb           = 0
                                  - controllerKey        = "1000"
                                  - controllerUnitNumber = "0"
                                  - diskPlacementRef     = "StoragePod:group-p100"
                                  - encrypted            = false
                                  - independent          = "false"
                                  - name                 = "vrauserqa-976-boot-disk"
                                  - persistent           = false
                                  - provisionGB          = "0"
                                  - provisioningType     = "thin"
                                  - type                 = "HDD"
                                  - vcUuid               = "634f89cd-bcf8-421b-bfa3-65f09557abca"
                                  - vm                   = "VirtualMachine:vm-710951"
                                },
                            ]
                        }
                      - totalMemoryMB             = 1024
                      - vcUuid                    = "634f89cd-bcf8-421b-bfa3-65f09557abca"
                      - zone                      = "Cluster1 / ESX Agents"
                      - zone_overlapping_migrated = "true"
                    }
                  - state      = "OK"
                  - type       = "Cloud.vSphere.Machine"
                },
            ]
          - createdAt        = "2021-04-07T20:12:42.249541Z"
          - createdBy        = "vrauser"
          - description      = ""
          - id               = "6162920c-d7df-4018-b843-0bb5e68873b7"
          - inputs           = {
              - cpuCount      = 1
              - totalMemoryMB = 1024
            }
          - lastUpdatedAt    = "2021-04-07T20:33:29.905193Z"
          - lastUpdatedBy    = "vrauser"
          - name             = "tf_vra_deployment"
          - orgId            = "c1cb7d03-37ee-4fbe-a052-6d2c4af5a8a8"
          - ownedBy          = "vrauser"
          - projectId        = "ae8d2e8e-ace6-4bf2-916a-bb10aa731d1b"
          - status           = "CREATE_SUCCESSFUL"
        }
    ) -> null

Do you really want to destroy all resources?
  Terraform will destroy all your managed infrastructure, as shown above.
  There is no undo. Only 'yes' will be accepted to confirm.

  Enter a value: yes

onefuse_vra_deployment.my_vra_deployment: Destroying... [id=1]
onefuse_vra_deployment.my_vra_deployment: Still destroying... [id=1, 10s elapsed]
onefuse_vra_deployment.my_vra_deployment: Still destroying... [id=1, 20s elapsed]
onefuse_vra_deployment.my_vra_deployment: Still destroying... [id=1, 30s elapsed]
onefuse_vra_deployment.my_vra_deployment: Still destroying... [id=1, 40s elapsed]
onefuse_vra_deployment.my_vra_deployment: Destruction complete after 43s

Destroy complete! Resources: 1 destroyed.