Gitlab scaffolding not working

Expected Behavior

When I configure the Gitlab settings in the scaffolding plugin, I expect to be able to target Gitlab for destination of scaffolding templates.

Current Behavior

Scaffolding a project using a template that targets Gitlab fails at several points.

1. Utilizing the ‘url’ resource type results in the error:
2. If specifying ‘gitlab’ resource type (no longer supported, but hackable by setting the annotation on the template), the plugin fails with “no auth”
3. The config used by the Gitlab code is deprecated catalog.processors.gitlabApi.privateToken, and causes the backend to fail with error:

Error: Using deprecated configuration for catalog.processors.gitlabApi, move to using integrations.gitlab instead

Possible Solution

1. Update the Scaffolding to auto-detect gitlab resource type for type: url
2. Update the Scaffolding to use the non-deprecated config locations

Steps to Reproduce

1. run the create-app
2. add gitlab config
3. try to create a template

integrations:
  gitlab:
    - host: gitlab.com
      token:
        $env: GITLAB_TOKEN
...
scaffolder:
  gitlab:
    api:
      baseUrl: https://gitlab.com
      token:
        $env: GITLAB_TOKEN
    visibility: internal # or 'internal' or 'private'
...
catalog:
  rules:
    - allow: [Component, API, Group, User, Template, Location]
  locations:
    - type: url
      target: https://gitlab.com/somegroup/somerepo/-/blob/master/template.yaml
      rules:
        - allow: [Template]

Context

I’m trying to use Backstage with Gitlab.

Your Environment

n/a

[freben]

@adamdmharvey We’ll have a larger stab at rewriting all of this in the beginning of next year. The way that it deduces credentials should be overhauled (and tied to GitHub apps and similar where possible), and AT LEAST be unified to look the same across the various classes.

[freben]

Hoping that this fixes it for you https://github.com/backstage/backstage/pull/3778

It tries to fall back to the token in integrations if there is one. The publisher does not yet do that though, so it’s best to stay with the particular token passed in scaffolder.gitlab.api.token instead.