Move from aws cli v1 to aws cli v2 #20
Closed
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
wojciech12
force-pushed
the
aws-cli-v2-support-in-runner
branch
from
959b134 to
319ba95
Compare
|
Implemented in #34 The build takes ~60 minutes on ARM, so I extracted that process to another repository. 🙂 Closing this. |
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.
The AWS CLI team still works on building aws cli v2 from the source, see: aws/aws-cli#6785 . Adding the AWS CLI v2 to the package repository might take some time.
The easiest way found by the community is to use PyInstaller, see aws/aws-cli#4685 (comment).
In this PR, we follow this approach, we use PyInstaller in a builder image to build the AWS CLI v2 and then copy it to the final image.