29 lines
2.8 KiB
YAML
29 lines
2.8 KiB
YAML
|
# This is a template for a feature deprecation
|
||
|
|
# A deprecation typically occurs when a feature or capability is planned to be removed in a future release.
|
||
|
|
# Deprecations should be announced at least two releases prior to removal. Any breaking changes should only be done in major releases.
|
||
|
|
#
|
||
|
|
# Below is an example of what a single entry should look like, it's required attributes,
|
||
|
|
# and what types we expect those attribute values to be.
|
||
|
|
#
|
||
|
|
# For more information please refer to the handbook documentation here:
|
||
|
|
# https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations
|
||
|
|
#
|
||
|
|
# Please delete this line and above before submitting your merge request.
|
||
|
|
|
||
|
|
- name: "Changes to the `CI_JOB_JWT`" # The name of the feature to be deprecated
|
||
|
|
announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated.
|
||
|
|
announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
|
||
|
|
removal_milestone: "15.0" # The milestone when this feature is planned to be removed
|
||
|
|
removal_date: # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
|
||
|
|
breaking_change: true # If this deprecation is a breaking change, set this value to true
|
||
|
|
reporter: dhershkovitch # GitLab username of the person reporting the deprecation
|
||
|
|
body: | # Do not modify this line, instead modify the lines below.
|
||
|
|
The `CI_JOB_JWT` will be updated to support a wider variety of cloud providers. It will be changed to match [`CI_JOB_JWT_V2`](https://docs.gitlab.com/ee/ci/variables/predefined_variables.html), but this change may not be backwards compatible for all users, including Hashicorp Vault users. To maintain the current behavior, users can switch to using `CI_JOB_JWT_V1`, or update their configuration in GitLab 15.0 to use the improved `CI_JOB_JWT`.
|
||
|
|
# The following items are not published on the docs page, but may be used in the future.
|
||
|
|
stage: # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
|
||
|
|
tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
|
||
|
|
issue_url: # (optional) This is a link to the deprecation issue in GitLab
|
||
|
|
documentation_url: # (optional) This is a link to the current documentation page
|
||
|
|
image_url: # (optional) This is a link to a thumbnail image depicting the feature
|
||
|
|
video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
|