Skip to content

Update VS Code Duo Pro entitlements outside of documentation

Description

Outside of the documentation, the VS Code extension mentions Duo Pro in other places. We need to make sure these are accurate and in line with the messaging of https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/issues/1300+

Where I need help

package.json was not included in !2607 (merged), but it might need changes. The section that starts at line 274 has GitLab Duo Pro as the title, but refers to Code Suggestions. The table at https://docs.gitlab.com/user/gitlab_duo/#summary-of-gitlab-duo-features says Code Suggestions is part of GitLab Duo Core now. Someone who understands the logic of this file should check to see what, if anything, we need to do here:

    "configuration": [
      {
        "id": "duo",
        "title": "GitLab Duo Pro",
        "order": 1,
        "properties": {
          "gitlab.duoCodeSuggestions.enabled": {
            "description": "GitLab Duo Code Suggestions",
            "type": "boolean",
            "order": 1,
            "default": true

Also, desktop.package.json mentions another entitlement that may be out of date:

                "type": {
                  "type": "string",
                  "description": "The type of GitLab items to return. If 'snippets' is selected, no other filters work. Epics available only on GitLab Ultimate or GitLab Gold.",
                  "enum": ["issues", "merge_requests", "epics", "snippets", "vulnerabilities"],
                  "default": "merge_requests"

Marketplace listings

Review each of these. Make sure the entitlements are correct, AND mention that Duo is a paid feature. Some of these will require assistance from the PM.

Related Issues

Checklist

Summary

Steps to reproduce

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

Possible fixes

Edited by Amy Qualls