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.

Sign up for GitHub

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

Jump to bottom

[8.2](backport #31014) [libbeat][aws] Fix AWS config initialization issue when using a role #31183

Merged
merged 1 commit into from
Apr 7, 2022
Merged

[8.2](backport #31014) [libbeat][aws] Fix AWS config initialization issue when using a role #31183

merged 1 commit into from
Apr 7, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 6, 2022 •
edited by zube bot
Loading

This is an automatic backport of pull request #31014 done by Mergify.

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

@zmoog
[libbeat][aws] Fix AWS config initialization issue when using a role (#…
6ed7916 
…31014)

* Move assume role to AWS config initialisation

* Wrap default aws config errors using std library

(cherry picked from commit cb5a951)
@mergify mergify bot requested a review from a team as a code owner April 6, 2022 10:11
@mergify mergify bot added the backport label Apr 6, 2022
@mergify mergify bot assigned zmoog Apr 6, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 6, 2022
@botelastic
Copy link

botelastic bot commented Apr 6, 2022

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

@elasticmachine
Copy link
Collaborator

elasticmachine commented Apr 6, 2022 •
edited by jenkins-beats-ci bot
Loading

💚 Build Succeeded

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

  • Start Time: 2022-04-07T13:01:55.529+0000

  • Duration: 57 min 49 sec

Test stats 🧪

Test Results
Failed 0
Passed 263
Skipped 42
Total 305

💚 Flaky test report

Tests succeeded.

🤖 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!)

@rdner
Copy link
Member

rdner commented Apr 7, 2022

/test

@rdner
Copy link
Member

rdner commented Apr 7, 2022

@zmoog any idea why the tests are failing?

@zmoog
Copy link
Contributor

zmoog commented Apr 7, 2022

@rdner no, I'm looking into it, the error seems unrelated to the changes introduced by this PR.

@zmoog
Copy link
Contributor

zmoog commented Apr 7, 2022

/test

@rdner rdner merged commit 502d26b into 8.2 Apr 7, 2022
@rdner rdner deleted the mergify/bp/8.2/pr-31014 branch April 7, 2022 13:59
@zmoog
Copy link
Contributor

zmoog commented Apr 7, 2022

Hey, thanks again @rdner! I was about to rebase it... this PR was initially created at a bad timing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@zmoog zmoog

Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@elasticmachine @rdner @zmoog