Content is a collection of files that contains definitions that represent software defined services.

After you add a content endpoint to one or more environments, you can manage the software-defined content that each environment contains. You can use vRealize Suite Lifecycle Manager to perform the following operations on content:
  • Capture content from an endpoint
  • Deploy to test and run unit tests
  • Check-in content
  • Release content to production

For example, a YAML file for a vRealize Automation blueprint or an XML file for a vRealize Orchestrator workflow. Content is linked together so that when you capture a vRealize Automation blueprint, all dependencies are also displayed in the content catalog, and they can each have their own versions. vRealize Suite Lifecycle Manager displays dependency information within each content version. The / Characters cannot be used in the name for Topology or Text ResourceKind Metrics as the export fails.

vRealize Suite Lifecycle Manager does not support an Azure machine in content management for testing and releasing content. XaaS blueprint "Azure Machine" is shipped by default with vRealize Automation. However, transfer of XaaS blueprint between vRealize Automation environments is not supported.

Content Issues that you might encounter

  • When transferring a customization spec between vCenter servers the password fields cannot be decrypted by the target. This causes deployments that depend on custom specs with passwords to fail. You can manually enter the correct value in the Administrator password field after customization spec is deployed by the Lifecycle Manager pipeline.
  • When a symptom definition is setup with REGEX or NOT_REGEX, the import fails using the vRealize Operations Manager APIs with the following error. Error releasing Operations-Symptom message= "Invalid request... #1 violations found.","validationFailures":[{"failureMessage":"Message Event Condition field 'operator' must be either EQ or CONTAINS. If a symptom uses REGEX, the content needs to be imported manually through Lifecycle Manager UI.
  • Content release from different versions of vRealize Operations Manager may fail. For example, content from 6.6 to 6.7 some content types may fail.
  • When transferring a customization spec between vCenter servers, the password fields cannot be decrypted by the target. This causes deployments that depend on custom specs with passwords to fail. You can manually enter the correct value in the Administrator password field after customization spec is deployed by the Lifecycle Manager pipeline.