Issue when linking GitLab using Service Tokens

[b-per]

When using service tokens to call the API to link a GitLab repo natively with dbt Cloud the connection is not set up correctly and require manually reconnecting the repo.

The same config works when using a user token.

This has been raised to the engineering team and should be automatically fixed without any action on this repo once the changes are done in dbt Cloud.

[github-actions[bot]]

This issue has been marked as Stale because it has been open for 90 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

[github-actions[bot]]

This issue has been marked as Stale because it has been open for 90 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

[kcd83]

Thanks for reporting. This is still an issue.

When diagnosing it I found the API for projects and/or repositories seems to show a little evidence of the problem

        "remote_backend": "gitlab",
        "git_clone_strategy": "deploy_token",
        "deploy_key_id": null,
        "repository_credentials_id": null,

Will not work, however setting this up as user in the UI I do see repository_credentials_id is set.

        "remote_backend": "gitlab",
        "git_clone_strategy": "deploy_token",
        "deploy_key_id": null,
        "repository_credentials_id": 6760,

The latter works fine

[b-per]

Hi @kcd83

Yes, this is still a problem, and the dbt Cloud team is aware of it, but there is nothing we can do just on the Terraform side for now. So, I keep this one as "blocked".

[github-actions[bot]]

This issue has been marked as Stale because it has been open for 90 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.