diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-11-10 00:10:00 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-11-10 00:10:00 +0300 |
commit | e1b5604609766f635f5029382ea018c612aa3186 (patch) | |
tree | fff466ae7fdf9edf47f84f539995292909ce8f94 /data | |
parent | efcaec8a140e2b93d1f43d5afd7a5c35cdd4dad7 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'data')
-rw-r--r-- | data/deprecations/ runner-s3-authenticationtype-nonexplicit-config-deprecation.yml | 12 | ||||
-rw-r--r-- | data/deprecations/disable_strict_host_key_checking.yml | 13 |
2 files changed, 25 insertions, 0 deletions
diff --git a/data/deprecations/ runner-s3-authenticationtype-nonexplicit-config-deprecation.yml b/data/deprecations/ runner-s3-authenticationtype-nonexplicit-config-deprecation.yml new file mode 100644 index 00000000000..01ca5839281 --- /dev/null +++ b/data/deprecations/ runner-s3-authenticationtype-nonexplicit-config-deprecation.yml @@ -0,0 +1,12 @@ +- name: "`AuthenticationType` for `[runners.cache.s3]` must be explicitly assigned" + announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. + announcement_date: "2021-11-22" + removal_milestone: "15.0" # the milestone when this feature is planned to be removed + body: | # Do not modify this line, instead modify the lines below. + In GitLab 15.0 and later, to access the AWS S3 cache, you must specify the `AuthenticationType` for [`[runners.cache.s3]`](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnerscaches3-section). The `AuthenticationType` must be `IAM` or `credentials`. + + Prior to 14.5, if you did not define the `AuthenticationType`, GitLab Runner chose a type for you. + stage: Verify + tiers: [Core, Premium, Ultimate] + issue_url: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28171 + documentation_url: https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnerscaches3-section diff --git a/data/deprecations/disable_strict_host_key_checking.yml b/data/deprecations/disable_strict_host_key_checking.yml new file mode 100644 index 00000000000..5a14120ea06 --- /dev/null +++ b/data/deprecations/disable_strict_host_key_checking.yml @@ -0,0 +1,13 @@ +- name: "Known host required for GitLab Runner SSH executor" + announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. + announcement_date: "2021-11-22" + removal_milestone: "15.0" # the milestone when this feature is planned to be removed + body: | # Do not modify this line, instead modify the lines below. + In [GitLab 14.3](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/3074), we added a configuration setting in the GitLab Runner config.toml. This setting, [`[runners.ssh.disable_strict_host_key_checking]`](https://docs.gitlab.com/runner/executors/ssh.html#security), controls whether or not to use strict host key checking with the SSH executor. + + In GitLab 15.0 and later, the default value for this configuration option will change from `true` to `false`. This means that strict host key checking will be enforced when using the GitLab Runner SSH executor. + stage: Verify + tiers: [Core, Premium, Ultimate] + issue_url: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28192 + documentation_url: https://docs.gitlab.com/runner/executors/ssh.html#security + |