The new permission is scoped to admins only.
The resolver now also returns a proper error
instead of null.

Changelog: changed
EE: true

Use new method in policies for ai features that are in ga.

Changelog: fixed
EE: true

Add namespace specs

Add user specs

Update global policy specs

Add respecting feature flag for enforced seats

Refactor troubleshoot ci policy

Refactor vulnerability policy

Update ask git policy

Add service name argument to method

For AI features in GA state, we need to check if they belong to group on correct tier,
but not if the experiment features flag is enabled. This MR adds new method that checks that.

Changelog: fixed
EE: true

Changelog: changed
EE: true

* Remove gitlab_duo_available? method since it's no longer used

Now that code suggestions are rolled out as part of Duo, we don't
need this feature flag to control release anymore. Remove the
self_managed_code_suggestions feature flag.

Changelog: other
MR: gitlab-org/gitlab!158440
EE: true

#463539

- instance level roles can be read by all registered users
- group level roles can be read by all members of a group

Replace Cloud Connector interface.

Use new CC interface instead of AcceessService.

Prior to this change, the `purchase_code_suggestions` feature flag was
enabled with the GA of Duo Pro back in February. Since then the feature
flag has been deemed stable.

This change removes the `purchase_code_suggestions` feature flag without
default enabling it given it only applies to GitLab.com.

Changelog: changed
EE: true

* If the feature flag 'duo_chat_requires_licensed_seat' is enabled for a
  root group, members of that root group will only be given Chat access
  if they also have a Duo Pro seat.
* This allows customers to opt into seat-based licensing for Chat before
  the "free access cut-off" date, which will be in the future.
* gitlab-org/gitlab#457090

This addresses two problems that this spec had:

- It was relying on the FF `ai_global_switch`, but it should be
  `ai_duo_chat_switch` as of 716d18b2.
- The 'when no neighbors are found' example was passing because
  TanukiBot was disabled, not because of an empty response

Changelog: fixed
EE: true

- all groups available for a group should be return
- a user who has permissions to add/update/remove a member in a group/project now sees all custom roles available for the project
- we now use one endpoint for both instance-level and group-level custom roles on invite modal

gitlab-org/gitlab#437848

Changelog: added
EE: true

- We are beyond the "service start date" of Feb 15
- logic previously was different for gitlab.com and self-managed but now
  every instance follows the same logic, which is that the user must be
  assigned a gitlab duo pro add-on seat
- group-level code suggestions setting no longer relevant, see
  #432282

- I thought this was done via gitlab-org/gitlab!145043
- Turns out, I forgot the `_` in the name of the ignored attribute and
  so it wasn't actually ignored. When I fixed the typo, the many
  instances where this setting was still referenced caused specs to fail.
  This MR fixes the typo and cleans up the reamining references.

Use CloudConnector::AccessService as SSoT.

In beta period access to code suggestions was configured on a group
level for GitLab.com. With GitLab Duo Pro add On rolled out, group
settings should no longer take effect. In order to align rollout
changes feature add_on_enabled is used

Changelog: other
EE: true

* Previously, Duo Chat was available to Ultimate plan users only.

Changelog: changed
EE: true

charlie ablett authored 1 year ago and Adam Hegyi committed 1 year ago

This change adds a helper method to check if ClickHouse database is
ready to be used.

* Enables code suggestions for users by default. This is .com change only.
* removes code_suggestions attribute from REST API

Changelog: removed
EE: true

This supports self-managed support for Code Suggestions by
cutting off instances that have not purchased the add-on
past the service start date.

Changelog: changed

Changelog: added
EE: true

When the flag is enabled, then user-level code_suggestion check is
skipped, and also this setting is not exposed to user.

EE: true

- only admin/group owners can read and admin member roles
- replace permission checks where needed

Chad Woolley authored 1 year ago and Alper Akgun committed 1 year ago

- For details, see: #431514

Alper Akgun authored 1 year ago and Enrique Alcántara committed 1 year ago

Changelog: added
EE: true