You can use vRealize Suite Lifecycle Manager to add content from an existing content endpoint.

Prerequisites

Verify that you have added a content endpoint.

Procedure

  1. On the My Services dashboard, click Content Management.
  2. Under Content, click ADD CONTENT.
    If a version has already been captured, a content can be added either with the Add Content button or with an inline capture.
  3. Select, test, or deploy the content package in addition to capturing it, and click PROCEED.
  4. Enter the capture details for the content package.
    1. From the Select Capture Endpoint drop-down menu, select one or multiple content types to capture.
    2. Enter a tag name and select Include all dependencies to capture any dependencies associated with the content.
      You can search for content by tag name.
    3. Enter the vRealize Orchestrator package name.

      Any spaces in the name are replaced with an _ underscore character and a vRealize Orchestrator package name.

      The vRealize Orchestrator package name is applicable only for vRealize Orchestrator or vRealize Automation content having some vRealize Orchestrator dependencies.

      If you provide a new name, all the vRealize Orchestrator contents are merged into one package. If you select an existing name from the drop-down menu, then a new version of the package is created and merges all vRealize Orchestrator contents to the version. If a package version already exists for the endpoint, the new package version will contain old and new content.

      If the vRealize Orchestrator package is not captured prior, a new version is created but the content might not be the same as the previous version. Deploy the added vRealize Orchestrator package to the vRealize Orchestrator content endpoint first to append the content. If you do not enter any package name, then the name of the vRealize Orchestrator package matches to the content that is captured with an added -vro as part of the name. All the discovered and captured vRealize Orchestrator content, including individual workflows in the content files, appear in the created vRealize Orchestrator package.
    4. If the content is ready for production, select Mark this version as production ready.
    5. Enter a description for the content version in the Comments field.
    6. Click Next.
    When you list the content for the first time for an endpoint, the system retrieves the content from the endpoint. After the content is captured, it is cached and the captured content is automatically refreshed every 30 minutes. You can select the Get latest content option to retrieve the content in between this 30 minute interval.
  5. If prompted, enter test details for the content endpoint.
    1. Select one or more content endpoints to specify the environments to run tests on.
    2. Select Deploy Content to deploy the content in the endpoint before running tests.
    3. Select Stop test deployment on first failure to stop the test deployment when it encounters an error.
    4. Select Run unit tests to run available unit tests on the content.
    5. Select Stop unit tests on first failure to stop testing if any unit test fails.
    6. Select a server to run unit tests on from the Select a Unit Test Server drop-down menu.
      You must have a vRealize Orchestrator test package imported to use a unit test server.
    7. Click Next.
  6. If prompted, enter the check-in details for the content package.
    1. Select one or more content endpoints from the Select Release Endpoints drop-down menu to specify the production environments where the system releases the content.
  7. Click SUBMIT.
    If you have selected a single content capture, you can view a single content pipeline. If you have selected multiple content captures, individual capture pipelines are deployed.