We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If there are no specific AWS static keys provided to the Provider struct, it results in:
Provider
operation error Route 53: ListHostedZonesByName, failed to sign request: failed to retrieve credentials: static credentials are empty
However, valid AWS keys are present in the enviornment:
AWS_ACCESS_KEY_ID= AWS_SECRET_ACCESS_KEY= AWS_SESSION_TOKEN=
The config.LoadDefaultConfig is sufficient to read these keys from the environment, so no special initialization is needed.
config.LoadDefaultConfig
The NewStaticCredentialsProvider should only be chained if AccessKeyId in Provider is a non empty value.
NewStaticCredentialsProvider
AccessKeyId
The text was updated successfully, but these errors were encountered:
Thanks for reporting this. I think this is a valid issue, will fix this soon.
Sorry, something went wrong.
fix: credentials static initialization
8d88cdf
ignore static credentials when they are not provided Fixes: #13
6c97f17
Successfully merging a pull request may close this issue.
If there are no specific AWS static keys provided to the
Provider
struct, it results in:However, valid AWS keys are present in the enviornment:
The
config.LoadDefaultConfig
is sufficient to read these keys from the environment, so no special initialization is needed.The
NewStaticCredentialsProvider
should only be chained ifAccessKeyId
in Provider is a non empty value.The text was updated successfully, but these errors were encountered: