Skip to content

Fix Self Hosted Duo Beta features not being available

Manoj M Jrequested to merge
mmj-shm-fix-alternate into master

What does this MR do and why?

For #541259 (closed)

A significant underlying issue was identified during troubleshooting of Self-Hosted beta features in this issue.

All Self-Hosted features currently in beta don't work properly in self-hosted environments due to permission check issues. This affects both air-gapped and online instances. The problem occurs because:

  • The system doesn't correctly use self_hosted_models as the service name during permission checks
  • Features like /include command and "Explain Vulnerability" don't appear or function properly
  • For some features like /troubleshoot, permission checks were okay, but the request was being made to AI Gateway with the wrong token, and hence the requests were failing.

This update changes the availability timeline for several GitLab Duo features including Root Cause Analysis, Vulnerability Explanation/Resolution, Discussion Summary, GitLab Duo for CLI, and Merge Request features. Additionally, the code adds a mapping system that connects service names to self-hosted feature names, allowing the platform to determine whether a particular AI service should use self-signed tokens when running in self-hosted environments.

References

Screenshots or screen recordings

Before After

How to set up and validate locally

MR acceptance checklist

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

Edited by Manoj M J

Merge request reports