AWS codeartifact requirements with python jobs

Description

Python AWS codeartifact OIDC variant/integration

Implementation ideas

Hi! using your templates we've come across several cases where in our pipelines we use codeartifact, the integration process is not completely clear with the Python component for the AWS CA registry, in contrast to the docker-ecr and aws-oidc which were intuitive and easy to use!

case 0:

building python packages at test stages that require internal dependencies from our codeartifact pypi registry our workaround: overriding parts of the component's job to perform: aws codeartifact login --tool pip --repository ${AWS_CODEARTIFACT_REPOSITORY_ENDPOINT} --domain ${AWS_CODE_ARTIFACT_DOMAIN} --domain-owner ${AWS_CODEARTIFACT_DOMAIN_OWNER} --region ${AWS_DEFAULT_REGION} which in itself isn't idle I assume since awscli needs to be present.

case 1:

publishing built python package to AWS codeartifact simliar to case 0, here we use either poetry or twine, which means the codeartifact credentials process is a bit different, but the idea stays the same

our workaround: creating our own code-artifact-pypi job and implement the required identification/release

case 2: (might be more related to Docker component, lmk if you want me to transfer over there)

when building an image that require installations from AWS codeartifact, we would usually pass a CODEARTIFACT_URL to the build args: Dockerfile ARG CODEARTIFACT_URL=${CODEARTIFACT_URL} RUN pip install --no-cache-dir our-package --extra-index-url ${CODEARTIFACT_URL} its unclear how should we create/achieve this using the component, since awscli is being used to create the CODEARTIFACT_URL

Thank you very much! wonderful product.