add logic to handle aws token for sso accounts

[mickmcgrath13]

Description

AWS SSO credentials require AWS_SESSION_TOKEN to work properly. This PR adds the env var to the /root/.aws/credentials file if the env var exists.

(note: I would expect the env vars alone to work, but I tested that, and they do not)

Fixes #162
Fixes #141

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

1. Locally mounting to the bitops repo to run against an ops repo by modifying the main deploy script and running aws commands before exit 0 before all the other code can run
2. Create a tagged bitops image and use in a pipeline runner

Logs
bitops command:

docker run --rm --name bitops \
-e AWS_ACCESS_KEY_ID="${AWS_ACCESS_KEY_ID}" \
-e AWS_SECRET_ACCESS_KEY="${AWS_SECRET_ACCESS_KEY}" \
-e AWS_SESSION_TOKEN="${AWS_SESSION_TOKEN}" \
-e AWS_DEFAULT_REGION="${AWS_DEFAULT_REGION}" \
-e ENVIRONMENT="example" \
-e TF_STATE_BUCKET="bitovi-operations-devops-training-example" \
-e DEFAULT_FOLDER_NAME="_default" \
-v $(pwd):/opt/bitops_deployment \
-v /Users/mick/Projects/Bitovi/bitops:/opt/bitops \
bitovi/bitops:v1.0.13

aws command

###########################################
##### DEBUGGING
###########################################
aws s3api list-buckets
exit 0
###########################################
##### END DEBUGGING
###########################################

without change

An error occurred (InvalidAccessKeyId) when calling the ListBuckets operation: The AWS Access Key Id you provided does not exist in our records.

With change

{
    "Buckets": [
        {
            "Name": "bitovi-operations-devops-training",
            "CreationDate": "2022-04-04T18:23:05+00:00"
        },
        {
            "Name": "bitovi-operations-devops-training-example",
            "CreationDate": "2022-04-04T21:03:18+00:00"
        }
    ]
}

Test Configuration:

• BitOps image tag used:
• Hardware:
• Tool:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation

[PhillypHenning]

👍 Great description of work. Thanks for keeping it clean.

👍 Code looks good. I can't see any potential problems arising

[dylan-bitovi]

👀 LGTM!