To perform content management, you must have content endpoints configured in your system. A content endpoint is an infrastructure endpoint in the SDDC that is targeted for the capture, test, and deployment of managed content in the form of a content package. Either a DevOps administrator or a content developer role is required to configure endpoints.
When adding the endpoint, you select appropriate policies to capture, test, or release content. Policies vary depending on the endpoint type
| Policy | Description |
|---|---|
| Allow content to be captured from the endpoint | Capture content from the endpoint and mark it as source content. |
| Allow unit tests to be run on the endpoint | Test content on the endpoint and acts as a unit test server. |
| Mark as Production Endpoint | Only applicable to a vSphere endpoint. Deploy content to production. When you mark a production endpoint, the Enable vCenter Template support is enabled. |
| Source-controlled Content only | Deploy content to an endpoint that comes only from a Source Control branch. Used in cases where the customization specification is code reviewed and checked in prior to release to a vCenter Server. This policy does not apply to vSphere templates because they are not checked in to Source Control. vSphere templates have versions in a vSphere Content Library. |
| Enable vCenter Template Support | Only applicable to a vSphere endpoint. Enable this option to open more fields. The vCenter Server details page stores information as to where the template is deployed in each vCenter Server. During the release process, the templates are retrieved from the local Content Library and turned into a Virtual Machine Template. |
| Select vRealize Orchestrator package | Only applicable to a vRealize Orchestrator endpoint. The vRealize Orchestrator package is also known as an overlay package. Use the overlay package to preserve environment specific settings such as locale and passwords in a configuration element. |
