Add extensibility actions to the Service Broker catalog

As a cloud administrator, you can add Cloud Assembly extensibility actions to Service Broker as a content source. The extensibility actions are created and managed in Cloud Assembly.

The actions are small scripts that perform lightweight tasks or steps. For example, rename a virtual machine or assign an IP address.

Prerequisites

• Verify that the actions you are adding are associated with a project, and that they are released. See How do I create extensibility actions.

Procedure

1. Import the released extensibility actions.
   1. Select Content and Policies > Content Sources, and click New.
   2. Click New, and then click Extensibility actions.
   3. Enter the Name for this content source.
   4. Select the Source project and then click Validate.
      The validation process verifies the number of released extensibility actions that are associated with the project in Cloud Assembly.
   5. Click Create and Import.
2. Share the imported actions with a project.
   1. Select Content and Policies > Policies > Definitions, and create a new content sharing policy.
   2. Enter a name for the content sharing policy.
   3. In the Scope list, select the project that includes the users who should be able to deploy the extensibility actions.
   4. In the Content sharing section, click Add Items and then select one or more actions to share with the project.
      You can select all the items imported from a content source or you can select individual items. To select only particular extensibility actions, select All Content in the Content Sources drop-down menu.
   5. In the Users section, select the users and user groups that you want to have access to the content.
      You can share the content with all users and groups in the project, or you can select individual users and groups.
   6. Click Create.
   The actions are added to the catalog where the project members can request them.
3. Verify that the action is available in the catalog to the members of the selected projects.
   1. Click Catalog, locate the imported extensibility action, and review the projects to ensure that the project you configured is included.
   2. Click Request and provide any required information.
   3. Click Submit.
   The provisioning process begins and the Deployments page opens with your current request at the top.
4. Monitor the provisioning process to ensure that the action runs successfully.
   1. Select Resources > Deployments and locate your deployed request.
   2. Monitor the card status until it is successful.

Results

The extensibility actions are imported into Service Broker and shared in the catalog.

What to do next

• If the deployment fails, click the deployment name and begin troubleshooting. See What can I do if a Service Broker deployment fails. If you are a Cloud Assembly cloud administrator, you can also do more extensive troubleshooting in Cloud Assembly What can I do if a Cloud Assembly deployment fails in Using and Managing VMware Cloud Assembly.
• If you want to control how long a deployment can exist, create a lease. See Setting up Service Broker policies.
• To provide more or fewer user inputs at request time, you can create a custom form. See Customize a Service Broker icon and request form.