Content lifecycle management in vRealize Suite Lifecycle Manager provides a way for release managers and content developers to manage 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. Content developers are not allowed to set a Release policy on end-points, only Release Managers can set policies.
Migration of contents or versions is not supported from an older instance to vRealize Suite Lifecycle Manager. The latest content version can be either source control or deploy to an endpoint before moving to vRealize Suite Lifecycle Manager . So that the same content can be re-captured from the endpoint in the new instance.
- 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.
|Product Name||Supported Version|
|vRealize Automation||7.2 and later|
|vRealize Orchestrator||7.x and later|
|VMware vSphere||6.0 and later|
|vRealize Operations Manager||6.6.1+ and later|
|Source Control servers||
- Content lifecycle management is deployed as part of vRealize Suite Lifecycle Manager on a single appliance. It has a new user interface and is tightly integrated with vRealize Suite Lifecycle Manager core services.
- Updated Pipeline services: Advanced capability to manage content to 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 vRealize Suite Lifecycle Manager. Each content version shows all its dependencies associated with it. For example, if a vRealize Automation Composite Blueprint has a dependency on 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. vRealize 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. We cannot deploy or release Automation-Component Profiles in vRealize Suite Lifecycle Manager to a target end point if the corresponding value set already exists on the end point.