Deprecate owasp_top_10 2017 enum values from GraphQL APIs

Deprecation Summary

We are removing support for OWASP 2017 grouping and switching over to 2021 grouping as part of it the underlying GraphQL API arguments also deprecated.

So deprecate and remove the 2017 values from https://docs.gitlab.com/ee/api/graphql/reference/#vulnerabilityowasptop10

Breaking Change?

This is not a breaking change, we are still supporting the ability to group by OWASP 2021 arguments for the same field. If the 2017 argument was used before the removal, we would return zero matching vulnerabilities.

Affected Topology

Self-managed and SaaS users

Affected Tier

GitLab Ultimate

Deprecation Milestone

In which milestone will this deprecation be announced?: %17.4

Planned Removal Milestone

As per the guidelines removal can be in %18.0

Parts of the schema marked for removal from the GitLab GraphQL API are first deprecated but still available for at least six releases. They are then removed entirely during the next XX.0 major release.

In which milestone will the feature or functionality be removed?: %18.0

Links

Corresponding feature deprecation issue: #458835 (closed)

Checklists

Click to expand

Labels

• This issue is labeled deprecation, and with the relevant ~devops::, ~group::, and ~Category: labels.
• This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.

Timeline

Please add links to the relevant merge requests.

• As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule: 14.8, 14.9, 14.10, 15.0 – 14.8 is the third milestone preceding the major release):
  • A deprecation announcement entry has been created so the deprecation will appear in release posts and on the general deprecation page.
  • Documentation has been updated to mark the feature as deprecated.
• On the major milestone:
  • The deprecated item has been removed.
  • If the removal of the deprecated item is a breaking change, the merge request is labeled breaking change.

Mentions

• Your stage's stable counterparts have been @mentioned on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.
  • To see who the stable counterparts are for a product team visit product categories
    • If there is no stable counterpart listed for Sales/CS please mention @timtams
    • If there is no stable counterpart listed for Support please mention @gitlab-com/support/managers
    • If there is no stable counterpart listed for Marketing please mention @cfoster3
• Your GPM or Director has been @mentioned so that they are aware of planned deprecations.