Remove deprecated ContainerExpirationPolicy Graphql type

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Deprecation Summary

For Developer role users do not see the cleanup sch... (#471341 - closed) we want to update authorization to ContainerExpirationPolicy and this involves changing some fields from null: false to null: true.

Based on the discussion, we decided to the deprecate the root field & create a new type with updated permissions: Adds ContainerTagsExpirationPolicy graphql type (!167126 - merged)

Breaking Change?

Affected Topology

Affected Tier

Deprecation Milestone

Planned Removal Milestone

%18.0

Links

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.014.8 is the third milestone preceding the major release):
  • On the major milestone:

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.
Edited by 🤖 GitLab Bot 🤖