layout | page_title | sidebar_current | description |
---|---|---|---|
vra7 |
VMware vRA7: vra7_deployment |
docs-vra7-resource-deployment |
Provides a VMware vRA7 deployment data source. This can be used to get a vra7_deployment |
Provides a VMware vRA7 deployment data source. This can be used to get a vra7_deployment
data "vra7_deployment" "this" {
deployment_id = "a0967161-d80f-220c-9c7a-5892025bc3ce"
}
data "vra7_deployment" "this" {
id = "a0967161-d80f-220c-9c7a-5892025bc3ce"
}
The following arguments are supported:
id
- The catalog item request id.deployment_id
- The resource id of the deployment.
businessgroup_id
- The id of the vRA business group to use for this deployment.businessgroup_name
- The name of the vRA business group to use for this deployment.catalog_item_id
- The id of the catalog item to deploy into vRA.catalog_item_name
- The name of the catalog item to deploy into vRA.description
- Description of the deployment.reasons
- Reasons for requesting the deployment.deployment_configuration
- The configuration of the deployment from the catalog item. All blueprint custom properties including property groups can be added to this block. This property is discussed in detail below.resource_configuration
- The configuration of the individual components from the catalog item. This property is discussed in detail below.lease_days
- Number of lease days remaining for the deployment. NOTE: lease_days 0 means the lease never expires.name
- The name of the deployment.request_status
- The status of the catalog item request.created_date
- The date when the deployment was created.expiry_date
- The date when the deployment will expire.owners
- The owners of the deployment.
This is a list of blocks that contains the machine resource level properties including the custom properties. Each resource_configuration block corresponds to a component in the blueprint/catalog_item. The sample blueprint has one vSphere machine resource/component called vSphereVM1. Properties of this machine can be specified in the config as shown in the example above. The properties like cpu, memory, storage, etc are generic machine properties and their is a custom property as well, called machine_property in the sample blueprint which is required at request time. There can be any number of machines and same format has to be followed to specify properties of other machines as well.All the properties that are required during request, must be specified in the config file.
The following arguments for resource_configuration block are supported:
component_name
- The name of the component/machine resource as in the blueprint/catalog_itemcluster
- Cluster size for this machine resourceparent_resource_id
- ID of the deployment of which this machine is a part ofrequest_id
- ID of the catalog item requestinstances
- List of the detailed state/view of the machine resources/instances/VMs within the deployment. This is a nested schema, discussed below
An instance is a VM in the list of VMs under a resource_configuration. For instance, for a component (say vSphere1), a resource_configuration block is added in main.tf. If the cluster size is 2, it will create 2 VMs and the instances will have both the VMs in the instances list.
resource_id
- ID of the machine resourcename
- Name of the resourcedescription
- Description of the resourceip_address
- IP address of the machineresource_type
- Type of resource. It can be a machine resource type (Infrastructure.Virtual) or a deployment type (composition.resource.type.deployment), etc.properties
- Map of the instance/VM properties fetched from the deployment
This block contains the deployment level properties including the custom properties and proprty groups. These are not a fixed set of properties but referred from the blueprint. From the example of the BasicSingleMachine blueprint, their is one custom property, called deployment_property which is required at request time. All the properties that are required during request, must be specified in the config file.