You can define a content release and manage source control access while you configure extensibility of your content release.
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.
vSphere Template Repository
- Create the Content Library (Publisher): The vSphere Template Repository points to a Content Library that is set up for publishing. For more details on how to setup a publisher Content Library, see vCenter Documentation:
- Create Content Library Subscribers: Each vCenter server that will have templates from LCM requires a Content Library to be configured which will Subscribe to the Published Library configured in Step 1. The following settings are required :
|Automatic Synchronization||You can enable this setting for automatic synchronization of the template metadata.|
|Subscription URL||This URL contains details about the publishers lib.json file. This will be available when you create a publisher in Step 1.|
Content tags are useful for a variety of reasons, to locate content within the UI, that is when you find all content with "BugFix-Task-1" tag or can be used for custom business logic during the release pipeline.
An example of this may be custom business logic implemented by a release manager - Don't Deploy Content to Endpoint B unless the Content has been deployed to Endpoint B, first this requires a custom pipeline/workflow to be implemented. If this rule is to be bypassed, for example, for Release Mangers to push Content straight to Endpoint B then a tag could be applied to the content. This tag should only be added by a Release Manager and not a Developer.