- 新しい順
- 投票が多い順
- コメントが多い順
Thanks for your response, and for sharing further details with me, Christopher.
-
The bug you are experiencing introduced in 3.14.11 was unintended. We were trying to fix another credential-related problem (where the
--profile
argument wasn't respected in the presence of env. vars.). I apologize that it has caused your CI system to fail. -
The EBCLI's behaviour is to use the value for
profile
present in .elasticbeanstalk/config.yml even if environment variables for the same are available. During (and only during)eb init
, this gets set toeb-cli
by the EBCLI if a--profile
is not explicitly passed. This subsequently gets set in .elasticbeanstalk/config.yml as the global profile for subsequent use (for instance, duringeb use
). -
The fix for the bug should be that the EBCLI not create a
eb-cli
credential pair when env. vars. for the access ID and secret key are available duringeb init
. This change shouldn't be a problem, however, it needs to be thought through before being committed to and made. -
Notwithstanding 3., for the time being, if you intend on using EBCLI 3.14.11, you can bypass the bug by setting the value for profile in .elasticbeanstalk/config.yml to
null
aftereb init
. Iseb init
something you need to perform time and again on Gitlab-CI? If not, the manual change to .elasticbeanstalk/config.yml should be a one-time thing and hence feasible, even though I wish you didn't have to do it.
Thanks,
Rahul.
Hi christopher-cp ,
I am curious to know if you are continuing to see the problem. I am unable to reproduce the problem. Specifically, I have been able to verify that:
- The
--profile
argument takes precedence over everything else - The environment variables
AWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
take precedence over everything else except--profile
(that is, eb use --profile PROFILE` will disregard the env. vars.)
I am curious to know what eb use --debugboto
shows you? Which profile exactly do you see requests being attempted with? You can determine this through a find operation inside the terminal on the substring "AKIA".
Thanks,
Rahul.
Hi Rahul,
thanks for your message!
Let me show you our deploy script (we use Gitlab-CI) first:
- pip install awsebcli
- mkdir -p ~/.aws
- echo '[profile eb-cli]' >> ~/.aws/config
# bug start: due to a bug introduced in awsebcli 3.14.11
- echo "aws_access_key_id = $AWS_ACCESS_KEY_ID" >> ~/.aws/config
- echo "aws_secret_access_key = $AWS_SECRET_ACCESS_KEY" >> ~/.aws/config
# bug end
- eb use XXX
- eb deploy
As you can see we don't use the "--profile" flag. But: there is a profile name in ".elasticbeanstalk/config.yml" (key: "global.profile"). I guess this must also be the reason why we need to create a ".aws/config". Does the property have the highest priority? Is it handled like "--profile"?
Cheers,
Christopher
Hi Christopher,
We've released the fix in 3.14.13. Let me know if the upgrade works.
Thanks,
Rahul.