update to good-citizen defaults#73
Conversation
|
Best reviewed: commit by commit
Optimal code review plan
|
noelmcloughlin
left a comment
There was a problem hiding this comment.
LGTM, thanks @javierbertoli go ahead and merge if Travis is passing.
One question - should letsencrypt/files/cli.ini.jinja be letsencrypt/files/default/cli.ini.jinja?
b477abe to
4b0a26c
Compare
Possibly, yes. But as the formula is not yet in-sync with I guess a new PR with a heavier refactor will come later 😄 |
Specifying `renew-by-default` in the config, regardless of True / False enables the flag. This causes certbot to force-renew on every timer run and means you will hit the rate-limit fairly quickly. A safer default is `keep-until-expiring` where the renew will only be done when it's actually advisable. `expand` allows an expanded domain list to renew correctly without forking a new domainset. This is something that most users will want.
Also specify `config` as a hash to make it easier to provide the config from multiple pillar values. Maintain backward compatibility (supplying `config` as a string) so that the formula continues to work as expected if a `config` string is already available. BREAKING CHANGE: `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.
closes saltstack-formulas#72 (ACMEv1 eol)
|
Merging as it got approved and the |
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
PR progress checklist (to be filled in by reviewers)
What type of PR is this?
Primary type
[build]Changes related to the build system[chore]Changes to the build process or auxiliary tools and libraries such as documentation generation[ci]Changes to the continuous integration configuration[feat]A new feature[fix]A bug fix[perf]A code change that improves performance[refactor]A code change that neither fixes a bug nor adds a feature[revert]A change used to revert a previous commit[style]Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)Secondary type
[docs]Documentation changes[test]Adding missing or correcting existing testsDoes this PR introduce a
BREAKING CHANGE?No.
Related issues and/or pull requests
#72
#63
Describe the changes you're proposing
This PR implements
configas a map and not only astring. This allows us to define default values indefaults.yaml. Added tests to check that the change is backward compatiblePillar / config required to test the proposed changes
Debug log showing how the proposed changes work
Documentation checklist
README(e.g.Available states).pillar.example.Testing checklist
state_top).Additional context