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.

Sign up for GitHub

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

Jump to bottom

Production ACME v2 endpoint is available. #37369

Merged
merged 1 commit into from Mar 13, 2018
Merged

Production ACME v2 endpoint is available. #37369

merged 1 commit into from Mar 13, 2018

Conversation

felixfontein
Copy link
Contributor

SUMMARY

There's now a ACME v2 endpoint with Let's Encrypt. This updates the documentation of the Let's Encrypt module accordingly.

Official announcement: https://community.letsencrypt.org/t/acme-v2-and-wildcard-certificate-support-is-live/55579

ISSUE TYPE

Docs Pull Request

COMPONENT NAME

letsencrypt

ANSIBLE VERSION

2.5.0, 2.6.0

ADDITIONAL INFORMATION

The current letsencrypt module doesn't work with the endpoint, due to the problem described here: #37165 (comment), so this shouldn't be backported to 2.5.0 until that is resolved.

@ansibot
Copy link
Contributor

ansibot commented Mar 13, 2018

cc @mgruener @resmo
click here for bot help

@ansibot ansibot added community_review In order to be merged, this PR must follow the community review workflow. docs This issue/PR relates to or includes documentation. module This issue/PR relates to a module. needs_triage Needs a first human triage before being processed. owner_pr This PR is made by the module's maintainer. support:community This issue/PR relates to code supported by the Ansible community. labels Mar 13, 2018
@felixfontein
Copy link
Contributor Author

According to @cpu in #37165 (comment), the Ansible 2.5 client will work with the official ACME v2 endpoint from Thursday March 15th on. So a backport is fine!

resmo
resmo approved these changes Mar 13, 2018
View reviewed changes
Copy link
Contributor

@resmo resmo left a comment

Choose a reason for hiding this comment

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

shipit

@ansibot ansibot added automerge This PR was automatically merged by ansibot. shipit This PR is ready to be merged by Core and removed community_review In order to be merged, this PR must follow the community review workflow. needs_triage Needs a first human triage before being processed. labels Mar 13, 2018
@ansibot ansibot merged commit 042ad70 into ansible:devel Mar 13, 2018
@felixfontein felixfontein deleted the letsencrypt-acme-v2-final branch March 13, 2018 21:09
@felixfontein
Copy link
Contributor Author

Thanks for handling this @resmo!

BTW, sould I open a PR for backporting this to 2.5? Also, what about #37276? Or is it already too late to get these two into the first 2.5 release?

@felixfontein felixfontein mentioned this pull request Apr 7, 2018
Merged
@dagwieers dagwieers added the crypto Crypto community (ACME, openssl, letsencrypt) label Feb 7, 2019
@ansible ansible locked and limited conversation to collaborators Apr 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@resmo resmo resmo approved these changes

Assignees
No one assigned
Labels
automerge This PR was automatically merged by ansibot. crypto Crypto community (ACME, openssl, letsencrypt) docs This issue/PR relates to or includes documentation. module This issue/PR relates to a module. owner_pr This PR is made by the module's maintainer. shipit This PR is ready to be merged by Core support:community This issue/PR relates to code supported by the Ansible community.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@felixfontein @ansibot @resmo @dagwieers