-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
Letsencrypt: improving documentation on second run #38135
Letsencrypt: improving documentation on second run #38135
Conversation
This meets what I would expect reading it for the first time. I like it! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shipit
… second run needs the data of the first (ansible#37884).
e334276
to
b828926
Compare
@apple4ever: good, thanks for taking a look! |
@resmo: this should also go into the |
@felixfontein perfect. I prefer if you do the PRs against stable-2.5, if you create a PR, it is okay to have more than one cherry-picks in the PR. shipit |
… second run needs the data of the first (ansible#37884). (ansible#38135) (cherry picked from commit 93fc99c)
… second run needs the data of the first (ansible#37884). (ansible#38135)
… second run needs the data of the first (ansible#37884). (ansible#38135)
SUMMARY
As @apple4ever noted in #37884, the module's documentation is unclear w.r.t. that the second run of the
letsencrypt
module needs the data provided by the first run. (This is a result of adding ACME v2 support, and that the old behavior could cause certificates to be issued more than once.)ISSUE TYPE
Docs Pull Request
COMPONENT NAME
letsencrypt
ANSIBLE VERSION
2.5.0