forked from martinhoefling/letsencrypt-formula
-
Notifications
You must be signed in to change notification settings - Fork 150
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
[BUG] ACMEv1 enf of life #72
Comments
Putting
instead of |
javierbertoli
added a commit
to netmanagers/letsencrypt-formula
that referenced
this issue
Jul 23, 2020
javierbertoli
added a commit
to netmanagers/letsencrypt-formula
that referenced
this issue
Jul 23, 2020
closes saltstack-formulas#72 (ACMEv1 eol)
javierbertoli
added a commit
to netmanagers/letsencrypt-formula
that referenced
this issue
Jul 23, 2020
closes saltstack-formulas#72 (ACMEv1 eol)
javierbertoli
added a commit
to netmanagers/letsencrypt-formula
that referenced
this issue
Jul 23, 2020
closes saltstack-formulas#72 (ACMEv1 eol)
saltstack-formulas-travis
pushed a commit
that referenced
this issue
Jul 23, 2020
# [1.0.0](v0.20.2...v1.0.0) (2020-07-23) ### Bug Fixes * **package:** amazonlinux defaults to python2 ([926c779](926c779)) * **server:** change server to ACMEv2 ([1fc79b8](1fc79b8)), closes [#72](#72) ### Documentation * **defaults:** update pillar.example to good-citizen defaults ([b889678](b889678)) ### Features * **config:** add sane defaults ([d9afac9](d9afac9)) * **package:** update default to py3 ([4c93c11](4c93c11)) ### BREAKING CHANGES * **config:** `config` can now be provided as a hash or a string; defaults are modified and, while sane and desirable, do change the behavior of the formula.
🎉 This issue has been resolved in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From Jun 2020 ACMEv1 is not supported any more and the formula fails.
The text was updated successfully, but these errors were encountered: