-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Update aws java sdk to support ecs task roles #25552
Update aws java sdk to support ecs task roles #25552
Conversation
Hi @matarrese, we have found your signature in our records, but it seems like you have signed with a different e-mail than the one used in yout Git commit. Can you please add both of these e-mails into your Github profile (they can be hidden), so we can match your e-mails to your Github profile? |
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
Thank you @karmi for your prompt reply. |
Any updates here? |
Solved by #26479 |
OMG! I'm very sorry I did not see your PR before I merged the other one. :shame: |
actually @matarrese #26479 does not update the SDK for |
True. @matarrese wanna add some missing bits to your PR? |
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
Hi @dadoonet, I missed the new updates on this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a comment.
Please run also gradle check
. It will most likely fail as the SHA1 changed for the new jars. Could you fix it as well?
plugins/repository-s3/build.gradle
Outdated
@@ -23,7 +23,7 @@ esplugin { | |||
} | |||
|
|||
versions << [ | |||
'aws': '1.10.69' | |||
'aws': '1.11.16' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you update it to 1.11.187
to align with what we have in #26479?
@matarrese Did you run |
Hi @dadoonet , now seems fine to me locally. |
jenkins test it please |
I'm surprised |
As I told you it failed with:
Run: gradle :plugins:repository-s3:updateSHAs
gradle :plugins:repository-s3:check And commit the changes. Thanks! |
jenkins test it please |
@elasticmachine test this please |
@rjernst could you please test this branch again? |
@elasticmachine test this please |
* master: (74 commits) Update version of TaskInfo header serialization after backport TEST: Tightens file-based condition in peer-recovery Correct backport replica rollback to 6.2 (elastic#28181) Backport replica rollback to 6.2 (elastic#28181) Rename deleteLocalTranslog to createNewTranslog AwaitsFix #testRecoveryAfterPrimaryPromotion TEST: init unassigned gcp in testAcquireIndexCommit Replica start peer recovery with safe commit (elastic#28181) Truncate tlog cli should assign global checkpoint (elastic#28192) Fix lock accounting in releasable lock Add ability to associate an ID with tasks (elastic#27764) [DOCS] Removed differencies between text and code (elastic#27993) text fixes (elastic#28136) Update getting-started.asciidoc (elastic#28145) [Docs] Spelling fix in painless-getting-started.asciidoc (elastic#28187) Fixed the cat.health REST test to accept 4ms, not just 4.0ms (elastic#28186) Do not keep 5.x commits once having 6.x commits (elastic#28188) Rename core module to server (elastic#28180) upgraded jna from 4.4.0-1 to 4.5.1 (elastic#28183) [TEST] Do not call RandomizedTest.scaledRandomIntBetween from multiple threads ...
@elasticmachine test this please |
@elasticmachine test this please |
@matarrese I think you need to remove the sha files you are adding to the licenses dir, as those were from a previous version of this PR when you had updated the sdk version. The test failure looks unrelated. If you remove those sha files, I will trigger tests once more, and if there are still unrelated failures I will pull and test this manually. |
Hi @rjernst , I have removed the generated sha files. |
@elasticmachine test this please |
@elasticmachine test this please |
This was actually picked up in #31864 by someone unaware of this old PR. I'm going to close this as it is no longer necessary, but thank you for the contribution @matarrese! |
Hi,
there are some failing tests, so it should not be considered as a ready to be reviewed pull request? Just to know if it's something related what you were talking about here: #23039