Skip to content

Add changes for GA ai features

Gosia Ksionek requested to merge mk-add-separate-method-for-ga-featues into master

What does this MR do and why?

In policies for SaaS for AI feature generate_commit_message we use a check that says if user is in any top-level group on the correct tier. However, the same check (any_group_with_ai_available?) checks if those groups on correct tier have experiment features enabled. This is a wrong check for GA features, that do not need to have this namespace setting enabled.

I swapped this check for a check if those groups on correct tier have duo features enabled. New check also respects feature flag we introduced with chat GA - there are customers that want AI features only with assigned seat mechanism (and they are weaving their "free period" bonus).

MR acceptance checklist

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

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Use GDK on in SaaS mode and enable AI features as per docs.
  2. No group that user is a member of can have experiment features enabled.
  3. Create an MR, try to merge it, create 'Generate commit message'.
  4. No error 🎉

solves #477177 (closed)

Edited by Gosia Ksionek

Merge request reports