| Hi Callum, yes still here  but just lacking the time to get in the headspace for this plugin. Luckily, New Year is quiet.. So, I had a look at your PR - and thanks for submitting, it has helped me understand a bit more about what's going on with the authentication. It seems that as the AWS authentication always happens on the Jenkins master, where the plugin runs, then it can only ever use creds supplied in the credentials stores or the local Jenkins master AWS configuration (env vars, .aws files, IAM roles). I did notice that the build job and pipeline environment variables are passed to the plugin though (via initialEnvironment), so rather than add a lot of new properties (as per your PR) I just modified the code to check this environment for the AWS_* environment variables. I then used the logic you had to determine the credentials provider. Changes here: https://github.com/jenkinsci/aws-parameter-store-plugin/commit/1a824f82d9ea9526b7eb6ff3f2cfdff2d22260be This should work for your requirements - if possible, can you check a custom build from this master branch? If not, I'll risk it and publish a new version. Cheers! |
