-
Notifications
You must be signed in to change notification settings - Fork 21
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
AWS instance profile is not used by plugin #21
Comments
I think it's just an oversight. I haven't used BeanStalk for quite a while, but if you can make.a PR, I'll merge and make a new release. |
I thought I did when I made the release. Here it is: https://plugins.gradle.org/plugin/fi.evident.beanstalk Are there some problems with the bits? |
It works just fine. My problem is solved (instance profile is used). I just missed updated version on https://plugins.gradle.org/plugin/fi.evident.beanstalk (I was checking only github releases https://github.com/EvidentSolutions/gradle-beanstalk-plugin/releases) |
Great! I just updated the changelog and forgot that I've previously updated GitHub release notes as well on this project. I'll do that as well. |
Oh, I forgot to push while releasing. That's embarrassing. 😆 |
My plugin run is failing (on jenkins instance) because
Unable to load AWS credentials from any provider in the chain
Checking source code (
DeployTask.deploy
) I see thatAWSCredentialsProviderChain
missescom.amazonaws.auth.EC2ContainerCredentialsProviderWrapper
(comparing tocom.amazonaws.auth.DefaultAWSCredentialsProviderChain
).Is there a reason for not including
EC2ContainerCredentialsProviderWrapper
(orcom.amazonaws.auth.InstanceProfileCredentialsProvider
) as last element of the chain?I have no profile configured on my jenkins EC2 machine- it contains just instance profile.
Without
InstanceProfileCredentialsProvider
in the chain, I cannot use plugin from jenkins.The text was updated successfully, but these errors were encountered: