Content lifecycle management in vRealize Suite Lifecycle Manager provides a way for release managers and content developers to manage software-defined data center (SDDC) content, including capturing, testing, and release to various environments, and source control capabilities through different source control endpoints that includes both GitLab and Bitbucket. Content Developers are not allowed to set Release policy on end-points only Release Managers can set policies.
Migration of contents or versions are not supported from an older instance to vRealize Suite Lifecycle Manager 8.0. The latest content version can be either source control or deploy to an endpoint before moving to vRealize Suite Lifecycle Manager 8.0. So that the same content can be recaptured 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.
- vRealize Automation 7.2 and later (vRealize Automation 8.0 is not supported as an endpoint) .
- vRealize Orchestrator 7.x and later. ( vRealize Orchestrator8.0 is not supported as an endpoint).
- VMware vSphere 6.0 and later.
- vRealize Operations Manager 6.6.1+ and later.
- Source Control servers:
- GitLab: All latest versions upto 11.6.5
- Bitbucket Server 6.5.1
- Bitbucket Cloud: All latest versions
- 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 multi-developer use case.
If there are dependencies between captured content packages, all the dependencies will be captured as first class objects in LCM. Each content version will show all its dependencies associated to it. For example, if avRealize 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 stale. vRealize Automation allows 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.