setup not creating fully up to date credentials file

[jpeeler]

I'm using a local runner, so the environment is not created from scratch for every job. The problem I'm experiencing is that when short lived credentials are utilized (aws_session_token) followed by a job using normal credentials, the existing session token is not removed from the configuration file. I would think it's okay to empty the credentials file before repopulating, but maybe a safer alternative is a move operation to a backup file? Or perhaps at a minimum the orb should warn that the file has not been fully updated.

aws-cli-orb/src/scripts/configure.sh

Lines 26 to 29 in 8cb46da

	if [ -n "${AWS_CLI_STR_SESSION_TOKEN}" ]; then
	aws configure set aws_session_token \
	"${AWS_CLI_STR_SESSION_TOKEN}" \
	--profile "$AWS_CLI_STR_PROFILE_NAME"

Sounds closely related to #139.

In the meantime, I suppose I'll ensure to remove the credentials file manually after a job is completed.