downgrade two dependencies

[darinpope]

Downgraded ssh-credentials and aws-java-sdk so the new features from 0.1.0 can be used with CloudBees Core 2.176.4.3

[chriskilding]

Tested locally and LGTM

[fimbulvetr]

This broke the fine-grained IAM policy support, because it downgraded sdk to < 1.11.623. Please see:

https://aws.amazon.com/blogs/opensource/introducing-fine-grained-iam-roles-service-accounts/
https://issues.jenkins-ci.org/browse/JENKINS-60110
https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts-minimum-sdk.html

That means this isn't very useful in a K8s Pod.

[chriskilding]

@darinpope Would you be able to see about upgrading the necessary bits in the Cloudbees distro so that I can move this plugin back up to the newer version of AWS SDK?

@fimbulvetr As a quick fix in the meantime, you could use a method like:

• Install the latest plugin version, but after that, specifically upgrade the AWS SDK plugin to a newer version in the Jenkins update center. (Jenkins will use the newest version that is installed.)
• Or roll back to the v0.1.0 .hpi with your favourite method (manual .hpi download, version pinning in your plugin management script etc)

[chriskilding]

@fimbulvetr I’ve reported the breaking change you’ve seen on JENKINS-60110 to try and bump its priority. Further discussion should go there.

[darinpope]

@chriskilding go ahead and bump it to what you need. The 0.1.1 release will still be ok.

[chriskilding]

@fimbulvetr I've now reverted this plugin to use aws-java-sdk 1.11.636 in the release 0.1.2 today. Could you try it out and just confirm that the plugin works once more on EKS?

[fimbulvetr]

Thanks @chriskilding. I should have the time to check this week. I'll let you know.

@fimbulvetr I've now reverted this plugin to use aws-java-sdk 1.11.636 in the release 0.1.2 today. Could you try it out and just confirm that the plugin works once more on EKS?