backstage-plugin-gitlab
backstage-plugin-gitlab copied to clipboard
loblaw-sre
Backstage plugin for Gitlab
This plugin was one that is showing [email protected] Requesting this plugin be migrated so that it will work with the 1.6 version of Backstage with the React Router 6.0 migration...
To start with - I am quite new to Backstage and recently started exploring it for one of our project. I would like to publish the vulnerability scan results (compliance...
The instructions in the plugin say to "Link to an existing entity file Example: https://github.com/backstage/backstage/blob/master/catalog-info.yaml" That URL produces the file in the UI (though not the raw version), but putting...
As per the discussion on https://github.com/loblaw-sre/backstage-plugin-gitlab/issues/25 this is the work I did to enable this functionality with a custom plugin, now within the context of the Gitlab plugin.
Very similar to a feature request for the Sentry Plugin in the main Backstage repo (Backstage/Backstage#13333) could you please add the ability for the Gitlab plugin to be able to...
It would be great if this plugin could collaborate with the `@backstage/plugin-catalog-backend-module-gitlab` to populate the project id in the entity module automatically if the user does not set the id...
Hi! :wave: Thank for this plugin, I've been using it but I'm working under a older version of Gitlab so sometimes we're missing some feature. This PR brings `duration` field...
I add the pipeline URLs for the old GitLab API, and I also fixed the problem with the baseUrl that was taken badly from the configuration file.
With the addition of auth middleware for certain implementations the requests made through frontend plugins get rejected if they don't contain a valid token as a part of the request....
This is because sometimes you don't use the same URL for backend and frontend. We use a CDN for the frontend and the backend lives in its own domain so...
