After you deploy catalog items, you can run actions in Service Broker to modify and manage the resources. The available actions depend on the resource type and whether the action is supported on a particular cloud account or integrated platform.
The available actions also depend on what your administrator entitled you to run.
As an administrator or project administrator, you can set up Day 2 Actions policies. See How do I entitle deployment users to Service Broker day 2 actions using policies.
You might also see actions that are not included in the list. These are likely custom actions that your administrator configured in Cloud Assembly.
|Action||Applies to these resource types||For these cloud accounts or integrations||Description|
Add additional disks to existing virtual machines.
If you add a disk to an Azure machine, the disk is deployed in the resource group that includes the machine. if it is a persistent disk, a new resource group is created.
||Cancel a deployment or a day 2 action on a deployment or a resource while the request is being processed.
You can cancel the request on the deployment card or in the deployment details. After you cancel the request, it appears as a failed request on the Deployments tab. Use the Delete action to clean up your deployment list.
Canceling a request that you think has been running too long is one method for managing deployment time. However, it is more efficient to set the Request Timeout in the projects. The default timeout is two hours. You can set if for a longer period of time if the workload deployment for a project requires more time.
Change the lease expiration date and time.
When a lease expires, the deployment is destroyed and the resources are reclaimed.
Lease policies are set in Service Broker.
||Changes to deployment owner to the selected user. The selected user must be a member of the same project that deployed the request.
If you want to assign a service administrator or project administrator as the owner, you must add them as a project member.
When a cloud template designer deploys a template, the designer is both the requester and the owner. However, a requester can make another project member the owner.
|Change Security Groups||Machines||
||You can associate and dissociate security groups with machine networks in a deployment. The change action applies to existing and on-demand security groups for NSX-V and NSX-T. This action is available only for single machines, not machine clusters.
To associate a security group with the machine network, the security group must be present in the deployment.
Dissociating a security group from all networks of all machines in a deployment does not remove the security group from the deployment.
These changes do not affect security groups applied as part of the network profiles.
This action changes the machine's security group configuration without recreating the machine. This is a non-destructive change.
Change security groups on a machine
|Connect to Remote Console||Machines||
||Open a remote session on the selected machine.
Review the following requirements for a successful connection.
If your connection attempt indicates that a connection can not be established with the host, you might be required to accept the self-signed certificate.
As an administrator, if you prefer to ensure trusted certificates, see KB2113926 to configure CA signed certificates for ESXi hosts.
|| Create a snapshot of the virtual machine.
If you are allowed only two snapshots in vSphere and you already have them, this command is not available until you delete a snapshot.
||Destroy a deployment.
All the resources are deleted and the reclaimed.
If a delete fails, you can run the delete action on a deployment a second time. During the second attempt, you can select Ignore Delete Failures. If you select this option, the deployment is deleted, but the resources might not be reclaimed. You should check the systems on which the deployment was provisioned to ensure that all resources are removed. If they are not, you must manually delete the residual resources on those systems.
||Delete the NAT port forwarding rules from an NSX-T or NSX-V gateway.|
|Machines and load balancers||
||Delete a machine or load balancer from a deployment. This action might result in an unusable deployment.|
||If the security is not associated with any machine in the deployment, the process removes the security group from the deployment.
||Delete a snapshot of the virtual machine.|
||Add or modify resource tags that are applied to individual deployment resources.|
|Get Terraform State||Terraform Configuration||
||Display the Terraform state file.
To view any changes that were made to the Terraform machines on the cloud platforms that they were deployed on and update the deployment, you first run the Refresh Terraform State action, and then run this Get Terraform State action.
When the file is displayed in a dialog box. The file is available for approximately 1 hour before you need to run a new refresh action. You can copy it if you need it for later.
You can also view the file on the deployment History tab. Select the Get Terraform State event on the Events tab, and then click Request Details. If the file is not expired, click View content. If the file is expired, run the Refresh and Get actions again.
You can run other day 2 action on the Terraform resources that are embedded in the configuration. The available actions depend on the resource type, the cloud platform that they are deployed on, and whether you are entitled to run the actions based on a day 2 policy.
||Power off the deployment without shutting down the guest operating systems.|
||Power off the machine without shutting down the guest operating systems.|
||Power on the deployment. If the resources were suspended, normal operation resumes from the point at which they were suspended.|
||Power on the machine. If the machine was suspended, normal operation resumes from the point at which the machine was suspended.|
Reboot the guest operating system on a virtual machine.
For a vSphere machine, VMware Tools must be installed on the machine to use this action.
||Change the load balancer size and logging level.
You can also add or remove routes, and change the protocol, port, health configuration, and member pool settings.
|NSX Gateway port forwarding||
||Add, edit, or delete the NAT port forwarding rules from an NSX-T or NSX-V gateway.|
|Refresh Terraform State||Terraform Configuration||
||Retrieve the latest iteration of the Terraform state file.
To retrieve any changes that were made to the Terraform machines on the cloud platforms that they were deployed on and update the deployment, you first run this Refresh Terraform State action.
To view the file, run the Get Terraform State action on the configuration.
Use the deployment history tab to monitor the refresh process.
||Remove disks from existing virtual machines.|
Force a virtual machine restart without shutting down the guest operating system.
Increase or decrease the CPU and memory of a virtual machine.
|Resize Boot Disk||Machines||
||Increase or decrease the size of your boot disk medium.|
|Resize Disk||Storage disk||
Increase the capacity of a storage disk.
||Shut down and restart a running machine.|
|Revert to Snapshot||Machines||
|| Revert to a previous snapshot of the machine.
You must have an existing snapshot to use this action.
|Run Puppet Task||Managed resources||
||Run the selected task on machines in your deployment.
The tasks are defined in your Puppet instance. You must be able to identify the task and provide the input parameters.
||Shut down the guest operating system and power off the machine. VMware Tools must be installed on the machine to use this action.|
||Pause the machine so that it cannot be used and does not consume any system resources other than the storage it is using.|
||Change the deployment based on the input parameters.
For an example, see How to move a deployed machine to another network.
|Update Tags||Machines and disks||
||Add, modify, or delete a tag that is applied to an individual resource.|