-
Task
-
Resolution: Fixed
-
Minor
-
None
-
-
238.v8fb_588a_2b_e67
Update the AWS Credentials plugin to use the AWS SDK for Java 2.x as provided by the AWS SDK for Java 2.x API plugin.
Confirm that the plugin works as expected with the new API.
- is blocking
-
-
- Closed
-
- links to
[JENKINS-73649] Update AWS Credentials plugin to use AWS SDK for Java 2.x
Basil Crow
added a comment - https://github.com/jenkinsci/aws-credentials-plugin/pull/254 provides an (untested) sketch of what this might look like.
Basil Crow
added a comment - https://github.com/jenkinsci/aws-credentials-plugin/pull/254 provides an (untested) sketch of what this might look like. Basil Crow
added a comment - Updated https://github.com/jenkinsci/aws-credentials-plugin/pull/254 to include a compatibility layer for dependent plugins. At this point the next step is to test manually on a real AWS account, focusing on the areas mentioned in https://github.com/jenkinsci/aws-credentials-plugin/pull/254 (including proxy authentication).
Basil Crow
added a comment - Updated https://github.com/jenkinsci/aws-credentials-plugin/pull/254 to include a compatibility layer for dependent plugins. At this point the next step is to test manually on a real AWS account, focusing on the areas mentioned in https://github.com/jenkinsci/aws-credentials-plugin/pull/254 (including proxy authentication). Basil Crow
added a comment - Fixed in https://github.com/jenkinsci/aws-credentials-plugin/pull/254. Released in 238.v8fb_588a_2b_e67.
Basil Crow
added a comment - Fixed in https://github.com/jenkinsci/aws-credentials-plugin/pull/254 . Released in 238.v8fb_588a_2b_e67 . 
This task is simple enough in theory, but there are a number of plugins that depend on the API provided by this plugin and might need to be updated in lockstep, depending on whether they use the changed API.
Another minor wrinkle is that the code to set HTTP proxy credentials has changed significantly from the v1 API. The documentation at https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/http-config-proxy-support.html describes how to deal with this, but the automated migration tool does not work here and some manual testing would likely be needed.