Update AWS gems

Renovate Comment

What are the next steps?

If you have been assigned as a reviewer to this Merge Request, please review this Merge Request with the same scrutiny as any community contribution:

Ensure that the dependencies updated meet our standards:
- Security: Dependencies do not contain malicious code
- Performance: Dependencies do not bloat the application code or prolong CI times unnecessarily
- Stability: Pipelines are passing
Review the changes introduced by the version upgrade. Consider using https://my.diffend.io to compare the two versions in case the updated dependency is either a Ruby Gem or a Node.js package, for example to compare pg_query 2.1.0 and 2.1.4.
Check if bundle install works locally, in the context of GDK.
If tests are passing and you've reviewed the updated dependencies, execute pipelines in the context of the main project

This MR is created from a fork, therefore not all jobs (e.g. Danger) might have been executed. Instead of hitting MWPS right away, you might want to wait until the pipeline you've just triggered finished.

Note: This might not be available in projects, in that case merging right away is an option
Merge away!

Troubleshooting

We have assembled some FAQs to help reviewers of these kind of merge requests.

Improve this message – The JSON comment below is for automation purposes.

{"labels":["maintenance::dependency","type::maintenance","automation:bot-authored","backend","Engineering Productivity"],"assignees":["gitlab-dependency-update-bot"],"reviewers":["stanhu"]}

assigned to @gitlab-dependency-update-bot

added 1 commit

d41106e0 - Update AWS gems

Compare with previous version

mentioned in issue #365045

added Engineering Productivity automation:bot-authored backend maintenancedependency typemaintenance labels

requested review from @stanhu

approved this merge request

@stanhu, thanks for approving this merge request.

This is the first time the merge request has been approved. To ensure full test coverage, a new pipeline will be started shortly.

For more info, please refer to the following links:

added pipeline:mr-approved label

merged

changed milestone to %16.5

@stanhu, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline was created more than 6 hours ago OR finished more than 2 hours ago, you should:

Ensure the merge request is not in Draft status.
Start a pipeline (especially important for Community contribution merge requests).
Set the merge request to auto-merge.

This is a guideline, not a rule. Please consider replying to this comment for transparency.

This message was generated automatically. You're welcome to improve it.

mentioned in commit 98ecef75

1 Message

CHANGELOG missing:

If this merge request needs a changelog entry, add the Changelog trailer to the commit message you want to add to the changelog.

If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Reviewer roulette

Changes that require review have been detected!

Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

Category	Reviewer	Maintainer
backend	Rad Batnag (`@radbatnag`) (UTC+8)	Roy Zwambag (`@rzwambag`) (UTC+2)

Please check reviewer's status!

Reviewer is available!
Reviewer is unavailable!

Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

Rubygems

This merge request adds, or changes a Rubygems dependency. Please review the Gemfile guidelines.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

This MR has changed Gemfile.checksum. GitLab team members should review the following dependency SAST scans:

If there appear to be any true-positive vulnerabilities identified, the report is misconfigured, or if you have questions, mention @gitlab-com/gl-security/appsec. If everything seems fine, react to this comment with a .

Please also review the Gemfile development AppSec guidelines. Thank you for keeping GitLab secure!

Generated by depSASTer. Open an issue to provide feedback.

Allure report

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for d41106e0

expand test summary

+-----------------------------------------------------------------------+
|                            suites summary                             |
+------------------+--------+--------+---------+-------+-------+--------+
|                  | passed | failed | skipped | flaky | total | result |
+------------------+--------+--------+---------+-------+-------+--------+
| Package          | 0      | 0      | 1       | 0     | 1     | ➖     |
| Data Stores      | 22     | 0      | 0       | 1     | 22    | ❗     |
| Plan             | 55     | 0      | 0       | 0     | 55    | ✅     |
| Govern           | 36     | 0      | 0       | 0     | 36    | ✅     |
| Create           | 46     | 0      | 1       | 0     | 47    | ✅     |
| Verify           | 8      | 0      | 0       | 0     | 8     | ✅     |
| Manage           | 13     | 0      | 1       | 0     | 14    | ✅     |
| Monitor          | 4      | 0      | 0       | 0     | 4     | ✅     |
| Framework sanity | 0      | 0      | 1       | 0     | 1     | ➖     |
+------------------+--------+--------+---------+-------+-------+--------+
| Total            | 184    | 0      | 4       | 1     | 188   | ❗     |
+------------------+--------+--------+---------+-------+-------+--------+

e2e-package-and-test: test report for d41106e0

expand test summary

+-----------------------------------------------------------------------+
|                            suites summary                             |
+------------------+--------+--------+---------+-------+-------+--------+
|                  | passed | failed | skipped | flaky | total | result |
+------------------+--------+--------+---------+-------+-------+--------+
| Data Stores      | 117    | 0      | 3       | 3     | 120   | ❗     |
| Create           | 547    | 0      | 101     | 16    | 648   | ❗     |
| Package          | 226    | 0      | 17      | 13    | 243   | ❗     |
| Plan             | 246    | 0      | 10      | 0     | 256   | ✅     |
| Framework sanity | 0      | 0      | 5       | 0     | 5     | ➖     |
| Manage           | 158    | 0      | 13      | 3     | 171   | ❗     |
| Fulfillment      | 8      | 0      | 69      | 0     | 77    | ✅     |
| Verify           | 144    | 0      | 15      | 0     | 159   | ✅     |
| Configure        | 1      | 0      | 9       | 0     | 10    | ✅     |
| Monitor          | 36     | 0      | 7       | 0     | 43    | ✅     |
| Govern           | 188    | 0      | 0       | 6     | 188   | ❗     |
| Release          | 15     | 0      | 3       | 0     | 18    | ✅     |
| Analytics        | 7      | 0      | 0       | 0     | 7     | ✅     |
| GitLab Metrics   | 2      | 0      | 1       | 0     | 3     | ✅     |
| Systems          | 8      | 0      | 0       | 0     | 8     | ✅     |
| Secure           | 6      | 0      | 3       | 0     | 9     | ✅     |
| ModelOps         | 0      | 0      | 6       | 0     | 6     | ➖     |
| Growth           | 0      | 0      | 6       | 0     | 6     | ➖     |
+------------------+--------+--------+---------+-------+-------+--------+
| Total            | 1709   | 0      | 268     | 41    | 1977  | ❗     |
+------------------+--------+--------+---------+-------+-------+--------+