cut dependence on deployment/check's extraTestScript #770

Open
opened 2026-03-02 13:03:54 +01:00 by kiara · 1 comment
Owner

so far many of our tests have used a testScript vs. extraTestScript distinction from shared code in deployment/check/common/nixosTest.nix.
we should recheck if some of that might no longer be needed in our post-nixops code.
in case tests would no longer depend on this, they could even be split out so as to live closer to their implementation code, like our service tests.

so far many of our tests have used a `testScript` vs. `extraTestScript` distinction from shared code in `deployment/check/common/nixosTest.nix`. we should recheck if some of that might no longer be needed in our post-nixops code. in case tests would no longer depend on this, they could even be split out so as to live closer to their implementation code, like our service tests.
Author
Owner

the acme node, the seeming central part of this common logic, when cleared of config does not make test apps-nixos itself fail (the seeming simplest test using with enableAcme = true), tho garage will show systemd service failure Failed to start Renew ACME certificate for *.localhost.

cutting use of this out itself tho just makes it fall back to security.acme.defaults.server's default of https://acme-v02.api.letsencrypt.org/directory, which seems to fail stating timed out resolving 'acme-v02.api.letsencrypt.org/A/IN.

it would be nice however to at least shift this type of configuration to our resources, unifying our handling of this through our data model.

the `acme` node, the seeming central part of this common logic, when cleared of config does not make test `apps-nixos` itself fail (the seeming simplest test using with `enableAcme = true`), tho garage will show systemd service failure `Failed to start Renew ACME certificate for *.localhost`. cutting use of this out itself tho just makes it fall back to `security.acme.defaults.server`'s [default of](https://search.nixos.org/options?channel=unstable&query=security.acme.defaults.server&show=security.acme.defaults.server) `https://acme-v02.api.letsencrypt.org/directory`, which seems to fail stating `timed out resolving 'acme-v02.api.letsencrypt.org/A/IN`. it would be nice however to at least shift this type of configuration to our `resources`, unifying our handling of this through our data model.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#224 automated dev-ops workflows
fediversity/fediversity
Reference
fediversity/fediversity#770
No description provided.