Skip to content

Unify AvailableServices for gitlab.com

Nikola Milojevic requested to merge 148543-cloud-connector-available-services-for-com into master

What does this MR do and why?

Since we don't sync AccessData from CDOT for Gitlab.com, we will store the data in a separate data structure (access_data.yml) for Gitlab.com, and read from that structure instead of the CloudConnector::AccessData database record.

As Gitlab.com is self-issuing the access tokens for CloudConnector, and we are going to filter chat tools/UP on Ai Gateway, we need a mechanism to issue a token with proper scopes, based on end-user access to the specific unit-primitive (we need to check the purchase record for user namespace and to check if the user has seat-assignment to issue a specific scope).

This MR introduces

  • 'access_data.yml' file which is the same format as cloud_connector.yml in CDOT
  • Introduces GitlabCom/AccessDataReader that parse access_data.yml and builds GitlabCom/AvailableServiceData
  • GitlabCom/AvailableServiceData is responsible for self-issuing a token with UP scopes based on end-user permissions

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Edited by Nikola Milojevic

Merge request reports