You can add source control server endpoint, vCenter publisher, pipeline extensibility and developer restrictions in content settings.
Source control access
To add a source control endpoint, provide a server for that source control from GitLab. For more information, see Add a source control server endpoint.
Note: You can add multiple server names for a source control server endpoint and only GitLab source control is supported for this version.
vSphere template repository
You can use vRealize Suite Lifecycle Manager to capture content from vCenter. The vSphere template repository is a content library within a designated vCenter instance. It stores all the templates that are captured and that can be managed by vRealize Suite Lifecycle Manager.
A best practice is to have this
vCenter instance close to where the templates would typically be captured, that is a development
vCenter for template authoring. You can specify a
vCenter instance to add as your endpoint. For more information, see
Add a vCenter content endpoint. The configuration model for the content library is as follows:
- Create the Content Library (Publisher): The vSphere template repository points to a content library that is configured for publishing. For information about configuring a publisher content library, see vCenter Documentation.
- Create the Content Library Subscribers: Each vCenter server that supports templates must support a content library that subscribes to the published library that you created in the above Step 1. The following settings are required:
| Setting | Description |
|---|---|
| Automatic Synchronization | Configure this setting for automatic synchronization of the template metadata. |
| Subscription URL | This URL contains details about the publishers lib.json file. It is available when you create the publisher in Step 1. |
| Authentication Off | Do not use this setting. You should require authentication. |
| Library content |
|
