DevLake should be configured automatically according to the Backstage components

[brunocribeiro]

Depends on: #65

As an OpenDORA plugin user

I want to be able to configure my deployment stages that count as a deployment

So that the DORA metrics are correctly calculated for a given component <> repository pair

• When a Backstage component is discovered/added to Backstage, a new data scope should be created in DevLake. Using annotations:
  • devoteam.com/opendora/project-url to specify the connection HttpUrlToRepo property. (string, required, URL including GitLab group)
  • devoteam.com/opendora/project-id to specify the connection gitlabId property. (string, required, stringified integer)
• When the data scope is added it should also create a scope config using annotations:
  • devoteam.com/opendora/deployment-pattern for selecting the stage that counts as a deployment for deployment frequency (string, required, regex)
  • devoteam.com/opendora/production-pattern for selecting the stage that counts as a production deployment (string, optional, regex)

Conditions:

The data scope and scope config should only be created if:

• The component has the devoteam.com/opendora/enabled annotation set to true
• There isn't already a data scope matching the devoteam.com/opendora/project-id / gitlabId .

References:

• https://backstage.io/docs/features/software-catalog/descriptor-format#annotations-optional
• https://backstage.io/docs/features/software-catalog/external-integrations#custom-processors
• https://devlake.apache.org/docs/Overview/References

[kylejwatson]

No longer important for the MVP in a 'generic' plugin, park for now to prioritise others.

[kylejwatson]

See #70 for implementation details.