aws-elastic-beanstalk-cli: [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
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 21
- Comments: 19 (4 by maintainers)
@halcarleton this issue is re-introduced with latest
awscliandawsebcliversions. 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?Thanks for the suggestion, but I was actually hoping for a proper solution from AWS. No offense, but I’m not really looking for yet another
pip<something>just to install AWS stuff that should simply work, out-of-the box, with plain oldpip.… and yet again: my working
Pipfile.lockhasawsebcliversion 3.19.3, withurllib3version 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?
awsebcli3.19.3 was installed withurllib31.26.3 before, but now, all of a sudden,urllib3must be <1.26?This is forcing me to freeze
awsebcli,boto3,botocore, andurllib3in thePipfile.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.
Closing this issue as awsebcli 3.17.1 has been released with a fix for this conflict.
Thank you for reporting this!
As of today, the issue still persists as
awscli 1.32.7 requires botocore==1.34.7 awsebcli 3.20.10 requires botocore<1.32.0,>1.23.41
What is the correct botocore version that is compatible with both?
If this happens again in the future, a very easy workaround is using the
pipxtool, just runpipx install awsebclihttps://pipxproject.github.io/pipx/Thanks for the workaround. I had gotten all this set up back in December and right after January 1 it got all messed up and this finally got me up an running again!