Add aws_signature_version attribute to packages config in gitlab.yml.example (!7375) · Merge requests · GitLab.org / GitLab · GitLab

The 17.0 major release is coming on May 16, 2024! This version brings many exciting improvements to GitLab, but also removes some deprecated features. We are introducing three breaking change windows during which we expect breaking changes to be deployed to GitLab.com. You can read more about it on our blogpost . The second breaking change window begins 2024-04-29 09:00 UTC and ends 2024-05-01 22:00 UTC.

Dmytro Zaporozhets (DZ) requested to merge dz-aws-signature-gitlab-yml into master Sep 14, 2018

What does this MR do?

Like https://gitlab.com/gitlab-org/gitlab-ee/commit/d16bc6358247774e32c785b878f38a5c7ba74a57 but for packages config

What are the relevant issue numbers?

https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/7269/diffs#note_101239537

Does this MR meet the acceptance criteria?

Changelog entry added, if necessary
Documentation created/updated
Tests added for this feature/bug
Conforms to the code review guidelines
Conforms to the merge request performance guidelines
Conforms to the style guides
Conforms to the database guides
EE specific content should be in the top level /ee folder
For a paid feature, have we considered GitLab.com plans, how it works for groups, and is there a design for promoting it to users who aren't on the correct plan?

Edited Sep 17, 2018 by Grzegorz Bizon