Skip to content
New issue

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

route53: Allow static credentials to be supplied #1746

Merged
merged 3 commits into from
Jan 15, 2023
Merged

route53: Allow static credentials to be supplied #1746

merged 3 commits into from
Jan 15, 2023

Conversation

vancluever
Copy link
Contributor

@vancluever vancluever commented Oct 30, 2022

This is incremental progress to implementing #1736, the first part being porting over certain providers (specifically route53 and lightsail) to use static credentials not derived from the environment.

This specifically adds support for the static chain where an access key ID, secret access key, and (optionally) a session token can be supplied manually.

@ldez ldez self-requested a review October 30, 2022 23:30
@vancluever vancluever marked this pull request as ready for review November 8, 2022 03:15
@vancluever
Copy link
Contributor Author

@ldez sorry for the delay, should be ready to review now!

@vancluever
Copy link
Contributor Author

@ldez looks like the failed tests are unrelated to route53 (unless they are depending on route53 for some reason that I don't know about. ./providers/dns/route53/ passes on my local machine.

@ldez ldez changed the title providers/dns/route53: Allow static credentials to be supplied route53: Allow static credentials to be supplied Nov 26, 2022
@ldez ldez added this to the v4.10 milestone Nov 26, 2022
vancluever and others added 2 commits January 15, 2023 23:11
This is incremental progress to implementing #1736, the first part being
porting over certain providers (specifically route53 and lightsail) to
use static credentials not derived from the environment.

This specifically adds support for the static chain where an access key
ID, secret access key, and (optionally) a session token can be supplied
manually.
@ldez
Copy link
Member

ldez commented Jan 15, 2023

Sorry for the time, I had to manage personal constraints that have slowed me down for a few months.

Copy link
Member

@ldez ldez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ldez ldez enabled auto-merge (squash) January 15, 2023 22:36
@ldez ldez merged commit 0122506 into go-acme:master Jan 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants