Pin awscli to v1.19.12 #549
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tonytw1
approved these changes
Feb 25, 2021
jorgeazevedo
force-pushed
the
ja-aws-cli-quickfix
branch
from
8196d6a to
52f9f61
Compare
See deprecation warning for these python versions https://aws.amazon.com/blogs/developer/announcing-the-end-of-support-for-python-3-4-and-3-5-in-the-aws-sdk-for-python-and-aws-cli-v1/ > On February 1, 2021, the AWS SDK for Python (Boto3 and Botocore) and the AWS Command Line Interface (AWS CLI) v1 will no longer support Python 3.4 and Python 3.5. We encourage you to upgrade to Python 3.6 or later (this deprecation doesn’t affect customers using Python 2.7). Issue - our version of pip installs the awscli package even though it now depends on an rsa package version that doesn't run in Python 3.5 Charming > [awscli v1.19.15 adjusted] our dependencies for rsa. We've moved our range to versions that no longer support Python 3.5. The AWS CLI did a deprecation campaign last year for dropping support of 3.4/3.5 at the beginning of Feb 2021. > > What's interesting is modern versions of pip for the last several years prevent what's happening here by refusing to install awscli-1.19.0+ on Python 3.5. Do you know offhand what version of pip your environment is using? > > In the meantime, we'd encourage you to either migrate to the AWS CLI v2, Python 3.6+, or pin to awscli<1.19.
jorgeazevedo
force-pushed
the
ja-aws-cli-quickfix
branch
from
52f9f61 to
7eed4b3
Compare
JamieB-gu
added a commit
that referenced
this pull request
Jul 21, 2023
This is the current latest version of the awscli. Attempts to solve a problem where the awscli was failing to install correctly. The problem was fixed in a recent version of the awscli: aws/aws-cli#8036 (comment) The awscli was previously pinned to a specific version due to a lack of support for Python 3.4/3.5: #549
JamieB-gu
added a commit
that referenced
this pull request
Jul 21, 2023
Changes the `awscli` install step to always install the latest version. Essentially the inverse change to #549 where the `awscli` was pinned to a specific version due to a lack of support for Python 3.4/3.5 Attempts to solve a problem where the awscli was failing to install correctly. The problem was fixed in a recent version of the `awscli`: aws/aws-cli#8036 (comment)
JamieB-gu
added a commit
that referenced
this pull request
Jul 21, 2023
Changes the `awscli` install step to always install the latest version. Essentially the inverse change to #549 where the `awscli` was pinned to a specific version due to a lack of support for Python 3.4/3.5 Attempts to solve a problem where the awscli was failing to install correctly. The problem was fixed in a recent version of the `awscli`: aws/aws-cli#8036 (comment)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
This is the last version supported by Python 3.4/3.5, which aws has deprecated.
See deprecation warning https://aws.amazon.com/blogs/developer/announcing-the-end-of-support-for-python-3-4-and-3-5-in-the-aws-sdk-for-python-and-aws-cli-v1/
And the issue being reported on the awscli github project. Essentially the version of pip being used (v8) installs the awscli package even though it now depends on an rsa package version that doesn't run in Python 3.5 Charming
How to test
How can we measure success?
Have we considered potential risks?
Images