Closed lorengordon closed 4 years ago
Did you verify all three conditions? v1-only, v2-only, and both
@eemperor good idea. i was verifying both, but should be easy enough to test each by running jobs overriding the env values...
@eemperor ok, built the three variations and grabbed the lines from the manifest to demonstrate:
v1-only:
aws-cli/1.18.169 Python/2.7.5 Linux/3.10.0-1062.1.2.el7.x86_64 botocore/1.19.9
v2-only:
aws-cli/2.0.61 Python/3.7.3 Linux/3.10.0-1062.1.2.el7.x86_64 exe/x86_64.centos.7
both v1 and v2:
aws-cli/1.18.169 Python/2.7.5 Linux/3.10.0-1062.1.2.el7.x86_64 botocore/1.19.9
aws-cli/2.0.61 Python/3.7.3 Linux/3.10.0-1062.1.2.el7.x86_64 exe/x86_64.centos.7
looks good! 👍
A few enhancements were made to AWSutils.sh that can be ported or reworked back in amigen8...
/usr/local/aws-cli
as this tracks more closely with the AWS install guides/usr/local/bin/aws1
and/usr/local/bin/aws2
to make it easier to use either when both versions are installed alongside each other/usr/local/bin/aws
will point to v2, as this is the default location for both installersIn addition, the installation of amzn utils rpms has been ported from AWScliSetup.sh. Very little was touched while porting it... Updates to match new variable names. And removed the epel setup, as that can happen outside this script as a prereq if it is needed.