Support for non-LE SSL Certs and non-Route53 DNS providers #659
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
certificate
,certificate_key
, andcertificate_chain
in the README documentation. (Should these be renamed to*_file
for clarity?)using_route53
option. Allows disabling Route53 record changes when doing acertify
GitHub Issues
#517 - Adds the ability to bypass the Route53 DNS record updates, allowing both custom certs and DNS
#401 - This functionality already exists, but wasn't exposed anywhere (to my knowledge) in the documentation