Disable Core for Self-Hosted When No CC AIG Detected
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
description: Gitlab Duo Self-Hosted customers with online Enterprise licenses can now use Core with Gitlab AI Vendor models to extend Gitlab Duo access to their entire user base. Duo Enterprise seat holders will be supported by configured self-hosted models, while users without Duo seats can access Duo Core functionality powered by GitLab's AI vendor models through GitLab.com's AI Gateway. This enables Self-Hosted customers to provide AI-powered features to their entire user base while maintaining control over enterprise data through self-hosted infrastructure for Enterprise licensed users.
documentation: ’https://docs.gitlab.com/administration/gitlab_duo_self_hosted/’
title: issue_url
Background
A Duo Self-Hosted design partner recently surfaced that the Core toggle is available to GitLab Duo Self-Hosted customers who have not configured the GitLab.com AIG. The only location that clarifies that Core will exfil data is in Gitlab documentation; it is not clear in the UI. This is a "dark pattern" that creates the potential for a Self-Hosted customer to enable Core without knowing that it would attempt to send data to GitLab.com.
Definition of Done
- Disable (gray out) Core toggle when there is no configuration with the Gitlab.com AIG (offline Enterprise license users)
- For cloud Enterprise license users, update in-UI text to clarify that Core is currently only usable with Gitlab.com AIG and GL AI Vendor Models