OpsVerse ONE
Integrations

GitLab Integration

this integration enables loading of catalog entities from gitlab com https //about gitlab com/ entities can also be added using either static catalog configurations https //backstage io/docs/features/software catalog/configuration or registering them using the catalog import button https //github com/backstage/backstage/tree/master/plugins/catalog import which is included in the opsverse one instance configuration to enable gitlab, change the following in the values yaml file in your opsverse one instance under devportal appconfig integration insert the following snippet gitlab \ host gitlab com token \<your gitlab token> under devportal auth insert the following snippet gitlabtoken \<your gitlab token> follow these steps to create your gitlab token gitlab plugin this plugin will bring in different gitlab cards based on your project to your opsverse one instance it gives an overview of the project, based on its project id , which includes contributors , language composition , merge request stats , merge requests list , gitlab pipeline stats etc your project id can be found under your project settings https //docs gitlab com/ee/user/project/settings/ component annotations to enable this plugin, the gitlab integration described above should be enabled in your opsverse one instance once this integration is enabled, the following annotation needs to be added to the metadata annotations section of the catalog info yaml file of every component that needs this integration gitlab com/project id <'your project id'> note spec type field in your can take values in \['website','library','service'] however to render gitlab entity, catalog must be of type service