Skip to content

Fixes provider id mismatch for cloud-connected self-hosted integrations#5032

Merged
d13 merged 1 commit into
mainfrom
bug/cloud-self-hosted-provider-id-mismatch
Mar 9, 2026
Merged

Fixes provider id mismatch for cloud-connected self-hosted integrations#5032
d13 merged 1 commit into
mainfrom
bug/cloud-self-hosted-provider-id-mismatch

Conversation

@d13

@d13 d13 commented Mar 9, 2026

Copy link
Copy Markdown
Member

The CloudGitLabSelfHosted and CloudGitHubEnterprise entries in ProvidersApi were spreading metadata from the wrong providersMetadata key, causing a provider id mismatch error when any API call went through ensureProviderTokenAndFunction.

  • CloudGitLabSelfHosted was using providersMetadata[GitCloudHostIntegrationId.GitLab] (id: gitlab) instead of providersMetadata[GitSelfManagedHostIntegrationId.CloudGitLabSelfHosted] (id: cloud-gitlab-self-hosted)
  • CloudGitHubEnterprise was using providersMetadata[GitSelfManagedHostIntegrationId.GitHubEnterprise] (id: github-enterprise) instead of providersMetadata[GitSelfManagedHostIntegrationId.CloudGitHubEnterprise] (id: cloud-github-enterprise)

@d13 d13 added this to the 17.11-patch milestone Mar 9, 2026
@d13 d13 linked an issue Mar 9, 2026 that may be closed by this pull request
@d13 d13 merged commit 8aa35c9 into main Mar 9, 2026
6 checks passed
@d13 d13 removed this from the 17.11-patch milestone Mar 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Start Work on an Issue fails for GitLab Self-Hosted

1 participant