[request]: fix awscli/awsebcli botocore conflict

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave “+1” or “me too” comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request When installing the latest versions of awscli and awsebcli, I’m getting a version conflict of botocore

pip3 install --upgrade --user awscli
pip3 install --upgrade --user awsebcli
ERROR: awscli 1.17.2 has requirement botocore==1.14.2, but you'll have botocore 1.13.50 which is incompatible.

Are you currently working around this issue? Workaround is to install an old version of awscli pip3 install --upgrade --user 'awscli<1.17' awsebcli

Or use something like virtualenv/pipenv

[spawn-guy]

@halcarleton this issue is re-introduced with latest awscli and awsebcli versions. will you be so kind to introduce a general fix for future releases instead of hotfixing this? Maybe, talk to “the other” team and produce a consensus?

awsebcli 3.19.0 requires botocore<1.18,>=1.17, but you'll have botocore 1.18.7 which is incompatible.
awscli 1.18.14 requires botocore==1.15.14, but you'll have botocore 1.17.63 which is incompatible.

[dennisvang]

… and yet again: my working Pipfile.lock has awsebcli version 3.19.3, with urllib3 version 1.26.3, but I cannot update:

ERROR: Cannot resolve urllib3 (1.26.5) due to conflicting parent dependencies: awsebcli => urllib3 (>=1.25.4,<1.26)

How can this be? awsebcli 3.19.3 was installed with urllib3 1.26.3 before, but now, all of a sudden, urllib3 must be <1.26?

This is forcing me to freeze awsebcli, boto3, botocore, and urllib3 in the Pipfile.

The “highly recommended” EB CLI installation scripts provide an inconvenient workaround. That is not a solution. So why is this issue closed?

As (one of) the largest cloud computing service provider(s) in the world, I would expect AWS to be able to fix this properly.