The Content Management service in VMware Aria Suite Lifecycle provides a way for release managers and content developers to manage their software-defined data center (SDDC). It includes content capturing, testing, and release to various environments, and source control capabilities through different source control endpoints that include GitHub, GitLab, and Bitbucket.

Migration of content or versions is not supported from an older instance to VMware Aria Suite Lifecycle. The latest content version can be either source controlled or deployed to an end point before moving to VMware Aria Suite Lifecycle.

Content developers cannot set a release policy on endpoints. Only release managers can set policies.

The following endpoint migrations and content settings are captured and supported:
  • All the endpoints are migrated along with source control user tokens.
  • Tags associated with the endpoints are migrated to new instance.
  • Pipeline stub configurations are migrated.
Note: When a cloud admin is granted a role of release manager or content developer, the cloud admin can only view the content management app inside the VMware Aria Suite Lifecycle. The cloud admin does not have permission to view other applications. A release manager and a content developer can view the content management app. As a workaround, you can perform all the cloud admin operations using the cloud admin role only and not provide additional permissions or role mapping.
You can use content life cycle management to replace the manual processes for managing the software-defined content. Supported content includes the following entities.
Product Name Supported Version
VMware Aria Automation all versions
VMware Aria Automation Orchestrator all versions
VMware vSphere all versions
VMware Aria Operations all versions
Source control servers
  • GitHub Enterprise Server: 2.20.15, 2.19.21, 2.21.6, 3.0, 3.10.2, and 3.11.4
  • GitLab: 12.2.12 (Enterprise Edition), 12.7, 12..8, and 15.11,13 (Enterprise Edition)
  • GitHub Cloud
  • Bitbucket Server 6.10, 7.0, 8.12, and 8.18.0
  • Bitbucket Cloud: Version 2.0
  • Microsoft Azure DevOps GIT
Note: VMware has tested the versions listed. Unlisted intermediate versions should also be supported.

Content life cycle management is one of the VMware Aria Suite Lifecycle services. It includes the capability to manage content and work with source control to support a multi-developer use case.

If there are dependencies between captured content packages, all the dependencies are captured as first class objects in VMware Aria Suite Lifecycle. Each content version shows all its dependencies associated with it. For example, if a VMware Aria Automation cloud template has a dependency on a property definition, there are two items in the content catalog, one for each content package. With independent version control for each content package, you can edit, capture, and release dependencies independently so that the content is never old. VMware Aria Automation allows you to define multiple named value sets within the size and image component profile types. You can add one or more of the value sets to machine components in a blueprint. You cannot deploy or release automation-component profiles in VMware Aria Suite Lifecycle to a target end point if the corresponding value set already exists on the end point.