S3 Orb broken on CircleCI Provided (non-python) images based on Ubuntu 20.04

[circleci-public]

S3 Orb broken on CircleCI Provided (non-python) images based on Ubuntu 20.04

[gmemstr]

I'd be in favour of moving to the newer version of the AWS CLI orb to leverage v2, I'm wary of implementing a fix that only addresses Debian/Ubuntu based images.

[felicianotech]

@kenperkins A fix was published in v1.1.1. In the future, this orb will use the AWS CLI v2 which includes its own Python and avoids most of this. For now, the standard installation via Pip occurs, even on a non-Python image.

[kenperkins]

Additional context: From the CircleCI Docs:

CircleCI Base Image

image: cimg/base:2020.01

This is a brand new Ubuntu-based image designed to install the very bare minimum. All of the next-generation convenience images that we will be releasing in the coming weeks are based on this image.

When to use it?

If you need a generic image to run on CircleCI, to use with orbs, or to use as a base for your own custom Docker image, this image is for you.

[kenperkins]

I did a quick test with the latest next-gen images (cimg) for node, ruby, rust, openjdk and php: they all are missing python as an interpreter. I expect this orb to not work an any of these as well, but I didn't test the full workflow.

[kenperkins]

Adding this command allows a work around with minimal steps

- run: sudo apt update && sudo apt install python3-venv python-is-python3

[felicianotech]

Looking into this.

[nraychaudhuri]

FYI. It failed for me on the sync command even though all the aws creds were in place. I was trying it for the first time. Reverted back to 1.0.11

[felicianotech]

My notes:

1. So far this doesn't appear to be an Ubuntu 18.04 vs 20.04 issue. Both images don't have a python binary because both images ship Python v3 by default, which is called with python3.
2. This orb is using an old version of the AWS CLI orb. In particular, the newer AWS CLI orb versions support the AWS CLI v2, which includes its own version of Python. It doesn't rely on any external version at all, which would solve this issue.
3. Alternatively, this issue with python not being available can be solved by checking for apt packages, which would then make this orb Debian/Ubuntu specific.

[kenperkins]

FWIW, We were previously using the 16.04 Machine Executor for much of our work due to the inability to mount volumes in the docker executor, but we've been moving away from that, partly because of the ancientness of 16.04, so that was how we came across this. I do think the orb should be resilient against this kind of problem however, having to push that responsibility to the user makes using the orb less appealing.

[felicianotech]

I do think the orb should be resilient against this kind of problem however, having to push that responsibility to the user makes using the orb less appealing.

I completely agree.

@gmemstr I can implement a solution but any opinion on which one is better?