Skip to main content

Questions about GitLab owners

How do I make owner name a real GitLab group?​

Import your GitLab groups, then write owner: group:gitlab/<name> in the catalog-info.yaml. The group:gitlab/ prefix is required. With owner: paiement-api alone, Astrolabe looks among its own groups and finds nothing.

If I enter one group, is only that group imported?​

No. That group and all its subgroups, at every level.

My company has several top-level groups, with no common parent. How do I get them all?​

Leave Group empty: on a self-managed GitLab, every group comes in. On gitlab.com, a group is required: there, you import one top-level group.

The group is several levels down. How do I write it?​

One separator per level.

  • Group set to acme: acme/paiement/api/v2 → owner: group:gitlab/paiement-api-v2
  • Group empty: acme/paiement/api/v2 → owner: group:gitlab/acme.paiement.api.v2

63 characters at most. In doubt, copy the name from the catalog.

What happens if I name a group that was not imported?​

The component is imported all the same. Its page shows a warning:

This entity has relations to other entities, which can't be found in the catalog. Entities not found are: group:gitlab/does-not-exist

OWNER shows gitlab/does-not-exist. The link leads to Warning: Entity not found. Nobody owns the component: it counts for no team.

Administration › Problems lists it too, in a Catalog block, with every component that names the same group. See Fix a component whose owner is not found.

Why does Catalog › Groups show api and not paiement-api?​

The list shows the group's GitLab name. owner needs the catalog name, which carries its parents. Open the group and copy its Entity Ref.

How often does the catalog read GitLab?​

Every 30 minutes. To read it now, click the play button (Run the GitLab collection now) in the Catalog collection table of Administration › Catalog.

Why does the screen say the teams will be renamed when I change Group?​

Because the name of an imported team comes from its path under the Group. With acme, acme/paiement/api is paiement-api; with acme/paiement, it is api. The owner of your components must follow. See Change the group later.

If I leave Branches empty, does it read every branch?​

No. Each project is read on its own default branch, and only on it. To read several branches, list them in Branches: for example master and backstage if your projects keep their catalog-info.yaml on one or the other. Astrolabe reads each project on each branch of the list.