You can 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, you can either select one or multiple content types to capture content.
    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 within the UI/API.
    3. Enter the vRO Package Name. Any spaces in the name are replaced with an _ underscore character and a vRO package name.
      The vRO Package Name is applicable only for vRealize Orchestrator or vRealize Automation content having some vRealize Orchestrator dependencies. The field is used for managing vRealize Orchestrator contents in an efficient way. If you provide any new name,then all the vRealize Orchestrator contents will be merged to one package. If you select an existing name from the drop-down menu, then a new version of the package will be created and merges all vRealize Orchestrator contents to the version. If there exists a package version already from that endpoint, the new version will have old contents in the previous version with new contents. This helps you to work incrementally on vRealize Orchestrator contents.
      If the vRealize Orchestrator package is not captured prior from a given content endpoint, then 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, appears in the vRealize Orchestrator package that is created.
    4. If the content is ready for production, select Mark this version as production ready.
    5. Enter a description for this content version in the Comments field.
    6. Click Next.
    Note: When you list the content for the first time for an endpoint, the UI retrieves the content from the endpoint. However, once you have captured then the content is cached and an auto refresh of content list runs in the background every 30 minutes. You can select the Get latest content option to retrieve the content in between this time.
  5. Enter test details for the content endpoint.
    This option appears only if you chose to test the content package.
    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. Enter the check-in details for the content package.
    This option appears only if you chose to check-in 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, then you can view a single content pipeline. If you have selected multiple content capture, then you can see the individual capture pipelines triggered for each of the content.