vRealize Suite Lifecycle Manager 2.0 content management allows the bulk release of content spanning different types where vSphere, vRealize Operations Manager, and vRealize Automation are deployed in one request. It provides an advanced filter option on the content type that is established from a specific content endpoint.

Multi contents are selected as part of a multi release request. Failure to deploy one of the selected contents, will not roll back deployed contents which are part of that request.


  1. On the left pane, select Content Management > Content Item.
  2. Expand the Filter Applied tree.
  3. Under the Content Filter section, you can filter by Tag, Type, Endpoint, and Policy to get to a subset of the content you want to view and deploy.

    Filter Type


    Content Filters

    This section lists the content filters.

    • Production Ready

    • Development Content

    • Tested

    • Source Controlled

    • Dependencies Captured

    Content Types

    This section lists the Content category based on the content type.

    Content Endpoints

    This section lists all the associated Content Endpoints.

  4. After you select a content filter, you can add a tag and then click Apply.

    A tag is associated when a content is created. A tag-based filter is useful when you want to search. However, you can still add the tag even after creating content. You can also manage bulk tags for all content and older versions.

  5. To save your filters, click Save.

    Developers can only view their filters and release managers can view all other RM filters. The saved filters can be edited or deleted.

    After you apply the content filters, the default content view changes to Content Version. When you provide a filter, you can locate a specific version of the content, for example, Production Ready Content with a specific tag and of a specific set of content types. For example, display only vSphere templates, vRealize Operations Manager dashboards and vRealize Automation Blueprints.

  6. To deploy the content to a release endpoint, follow the wizard.
  7. Select an appropriate endpoint to each type of content appears.

    Orchestrator endpoints are assumed by their parent automation instance. If there are standalone Orchestrator endpoints configured, then you can also deploy them.

  8. In a content pipeline, a new multi release pipeline is initiated, where it is queued and released when the system is available to process them.

    For each type of content, a separate multi release pipeline is started. All contents are grouped and are imported for performance. For example, all automation blueprints and any dependencies are downloaded from the LCM repository and released in one flow. The Pre and Post pipeline stubs support is available for the multi_release_pipeline.