-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
Update the release documentation #85369
Conversation
Certificates will be regenerated anew on the next renewal date. The credentials for simp-le are | ||
preserved and thus it is possible to roll back to previous versions without breaking certificate | ||
generation. | ||
Certificates will be regenerated on activation, no account or certificate will be migrated from simp-le. |
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.
simp_le
state and lego
state are stored in different directories no? or at different places? So rollback should work? if that isn't the case anymore than that's a new bug.
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.
We dont say it's backwards compatible. We just say that rollback is an option. Those are different things
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.
Ah yes, if that’s what you mean for "rollback". However:
- a new account will be recreated by lego anwyay, he won’t be able to use the one created by simp_le
- lego will generate new certificates when switching from simp-le to lego the first time, because it doesn’t use the content of /var/lib/acme/your_cert to make its decision. Switching back I don’t know (that will depend on how simp-le computes if a certificate is too old)
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.
We mean rollback in the sense of nixos-rebuild switch --rollback
. i.e. the switch to lego
doesn't destroy any simp_le
state so if something goes bad with upgrade, you can go back to 19.09
and figure out what went wrong
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.
Ok, I’ll put back the last line then
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.
Changed
6b6d30e
to
7c5fce5
Compare
@GrahamcOfBorg test acme |
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.
LGTM :) I'm a fan of well worded options, in hope that if the agent changes we can reuse/maintain them.
7c5fce5
to
7d7b6c1
Compare
Thanks! Maybe future work, but can we test this feature in a VM test? |
I agree. I already tried to understand how tests worked, but I’m not fully at ease with the language yet, it’s still new to me. If you think it’s necessary for this PR it may take me a bit longer to manage to write it (or someone else to write it) |
7d7b6c1
to
5eae566
Compare
It currently says that everything will be backward compatible between lego and simp-le certificates, but it’s not.
5eae566
to
b3e8c0e
Compare
@flokli : done |
Motivation for this change
See this comment on the issue: #84633 (comment)
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)