yacloud/acme.sh
1
0
Fork 0
mirror of https://github.com/acmesh-official/acme.sh.git synced 2025-04-29 19:32:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge e2f70722090a8a26fba876f14eb805c540c5074f into 40b6db6a2715628aa977ed1853fe5256704010ae

Browse Source
This commit is contained in:
Simon Blake 2025-04-03 04:14:09 +02:00 committed by GitHub
commit 5d9e7155fa
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
dnsapi/dns_aws.sh
View File

@ -31,6 +31,20 @@ dns_aws_add() {
_use_container_role || _use_instance_role
fi
# if not already set, attempt to get AWS creds from a local creds file.
# this is naive, it just grabs the first values from .aws/credentials
# it does not honour [sections] in the ini formatted credentials file.
if [ -z "$AWS_ACCESS_KEY_ID" ] || [ -z "$AWS_SECRET_ACCESS_KEY" ]; then
CREDFILE="${HOME}/.aws/credentials"
if [ -e "$CREDFILE" ]; then
AWS_ACCESS_KEY_ID=$(grep -m 1 -i AWS_ACCESS_KEY_ID "$CREDFILE" | cut -f 2 -d"=" | tr -d ' ')
AWS_SECRET_ACCESS_KEY=$(grep -m 1 -i AWS_SECRET_ACCESS_KEY "$CREDFILE" | cut -f 2 -d"=" | tr -d ' ')
fi
# todo: if the key is found in the creds file, then if we can assume it'll be there in the future,
# then there's likely no point saving it in the account config, so we should do what needs to be done
# to disable saving the AWS creds in the acme.sh config.
fi
if [ -z "$AWS_ACCESS_KEY_ID" ] || [ -z "$AWS_SECRET_ACCESS_KEY" ]; then
AWS_ACCESS_KEY_ID=""
AWS_SECRET_ACCESS_KEY=""