You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to be able to enable/disable the plugin on a per-component basis
So that I can control its visibility for a component as well as have custom repository name-matching
Reasoning: Currently, the OpenDORA tab shows up automatically in every component. The plugin should be enabled via the catalog, and disabled by default.
Also, the repository name (for component filtering on the API side) should be configurable via annotations to improve project -> component matching
Annotations to be used:
devoteam.com/opendora/project-id to specify the GitLab project configured in DevLake
devoteam.com/opendora/enabled to specify if the plugin should be enabled for this component.
brunocribeiro
changed the title
OpenDORA Plugin Tab visibility should be controlled via the catalog
OpenDORA Plugin component match should be configured via Backstage's catalog
Oct 12, 2023
As an OpenDORA Backstage Plugin user
I would like to be able to enable/disable the plugin on a per-component basis
So that I can control its visibility for a component as well as have custom repository name-matching
Reasoning: Currently, the OpenDORA tab shows up automatically in every component. The plugin should be enabled via the catalog, and disabled by default.
Also, the repository name (for component filtering on the API side) should be configurable via annotations to improve project -> component matching
Annotations to be used:
devoteam.com/opendora/project-id
to specify the GitLab project configured in DevLakedevoteam.com/opendora/enabled
to specify if the plugin should be enabled for this component.References:
The text was updated successfully, but these errors were encountered: