Allow self-managed instances to require licensed seats for Duo Chat
What does this MR do and why?
This MR introduces the ability for self-managed GitLab instances to require licensed seats for Duo Chat using the existing duo_chat_requires_licensed_seat_sm
feature flag. Before this MR, it was enabled globally due to Chat GA.
This is considered a bug worthy of patching because some customers will not be able to upgrade to the latest version due to this.
Here is a similar MR for .com
. The difference is: with this MR, it is configured only by an instance-wide feature flag, whereas in .com
, it can also be turned on or off per group.
Here is the MR on master.
Related to #457283 (closed)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch. -
The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes). -
* [ ] This MR has a severity label assigned (if applicable). -
Set the milestone of the merge request to match the target backport branch version. -
This MR has been approved by a maintainer (only one approval is required). -
Ensure the e2e:package-and-test-ee
job has either succeeded or been approved by a Software Engineer in Test.
Note to the merge request author and maintainer
If you have questions about the patch release process, please:
- Refer to the patch release runbook for engineers and maintainers for guidance.
- Ask questions on the
#releases
Slack channel (internal only).