-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
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
ACME test cleanups #85503
ACME test cleanups #85503
Conversation
Also add myself to maintainers and correct meta.homepage.
This was added in aade4e5, but the implementation of the ACME module has been entirely rewritten since then, and the test seems to run fine on AArch64.
Shimming out the Let's Encrypt domain name to reuse client configuration doesn't work properly (Pebble uses different endpoint URL formats), is recommended against by upstream,[1] and is unnecessary now that the ACME module supports specifying an ACME server. This commit changes the tests to use the domain name acme.test instead, and renames the letsencrypt node to acme to reflect that it has nothing to do with the ACME server that Let's Encrypt runs. The imports are renamed for clarity: * nixos/tests/common/{letsencrypt => acme}/{common.nix => client} * nixos/tests/common/{letsencrypt => acme}/{default.nix => server} The test's other domain names are also adjusted to use *.test for consistency (and to avoid misuse of non-reserved domain names such as standalone.com). [1] letsencrypt/pebble#283 (comment) Co-authored-by: Yegor Timoshenko <yegortimoshenko@riseup.net>
This lets us get early warning about any bugs or backwards-compatibility hazards in lego. Pebble will default to this in the future, but doesn't currently; see https://github.com/letsencrypt/pebble/blob/v2.3.0/README.md#strict-mode.
The resolver is mainly useful for the ACME server, and acme.nix uses its own DNS server to test DNS-01 challenges.
@emilazy I tried to Could you open a backport PR against 20.03 instead? |
@emilazy This did a great work on making the acme server infrastructure reusable for other vm tests that also involve acme certificates! ❤️ Do you have any plans on moving more of the tooling into I could imagine the Once the acme tooling is easy usable elsewhere, we could then stop setting |
Motivation for this change
The parts of #83474 that don't add new functionality. Should be backported to 20.03 on merge.
cc @flokli
@GrahamcOfBorg test acme
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)