Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump aws-sdk-go-v2 to v1.26 #38607

Closed
wants to merge 6 commits into from

Conversation

kaiyan-sheng
Copy link
Contributor

@kaiyan-sheng kaiyan-sheng commented Mar 26, 2024

Proposed commit message

This PR is to bump aws-sdk-go-v2 version to v1.26.0

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

…wTduXaeRKoyT2gZwY3YzXeGBLinmzyUeNoeqC6HGUz2cY5kYJxjGghqFKev0
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Mar 26, 2024
@botelastic
Copy link

botelastic bot commented Mar 26, 2024

This pull request doesn't have a Team:<team> label.

@kaiyan-sheng kaiyan-sheng changed the title Bump aws-sdk-go-v2 to v1.26.export artifactory_api_key=AKCpBsdi6c6QwZ… Bump aws-sdk-go-v2 to v1.26 Mar 26, 2024
Copy link
Contributor

mergify bot commented Mar 26, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @kaiyan-sheng? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

@elasticmachine
Copy link
Collaborator

elasticmachine commented Mar 26, 2024

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Duration: 112 min 1 sec

Test stats 🧪

Test Results
Failed 0
Passed 31497
Skipped 1894
Total 33391

Steps errors 13

Expand to view the steps failures

Show only the first 10 steps failures

x-pack/filebeat-goIntegTest - mage goIntegTest
  • Took 6 min 54 sec . View more details here
  • Description: mage goIntegTest
x-pack/filebeat-goIntegTest - mage goIntegTest
  • Took 2 min 14 sec . View more details here
  • Description: mage goIntegTest
x-pack/filebeat-goIntegTest - mage goIntegTest
  • Took 2 min 16 sec . View more details here
  • Description: mage goIntegTest
x-pack/filebeat-windows-2022-windows-2022 - mage build unitTest
  • Took 6 min 4 sec . View more details here
  • Description: mage build unitTest
x-pack/filebeat-windows-2022-windows-2022 - mage build unitTest
  • Took 1 min 16 sec . View more details here
  • Description: mage build unitTest
x-pack/filebeat-windows-2022-windows-2022 - mage build unitTest
  • Took 1 min 16 sec . View more details here
  • Description: mage build unitTest
x-pack/filebeat-windows-2016-windows-2016 - mage build unitTest
  • Took 6 min 0 sec . View more details here
  • Description: mage build unitTest
x-pack/filebeat-windows-2016-windows-2016 - mage build unitTest
  • Took 1 min 16 sec . View more details here
  • Description: mage build unitTest
x-pack/filebeat-windows-2016-windows-2016 - mage build unitTest
  • Took 1 min 16 sec . View more details here
  • Description: mage build unitTest
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: Error 'hudson.AbortException: script returned exit code 1'

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

Copy link
Contributor

mergify bot commented Apr 16, 2024

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b bump_aws_sdk_version upstream/bump_aws_sdk_version
git merge upstream/main
git push upstream bump_aws_sdk_version

@kaiyan-sheng
Copy link
Contributor Author

Closing this PR because of #39454

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants