Some checks failed
deploy-infra / deploy (push) Successful in 2m13s
/ check-pre-commit (push) Failing after 14s
/ check-data-model (push) Successful in 32s
/ check-mastodon (push) Successful in 23s
/ check-peertube (push) Successful in 21s
/ check-panel (push) Successful in 1m31s
/ check-proxmox-basic (push) Successful in 36s
/ check-deployment-basic (push) Successful in 32s
/ check-deployment-cli (push) Successful in 45s
/ check-deployment-panel (push) Successful in 1m53s
/ check-deployment-model-ssh (push) Successful in 24s
/ check-deployment-model-nixops4 (push) Successful in 34s
/ check-resources (push) Successful in 4m12s
test deployments using data obtained through the data model in VMs. caveats: - SSH currently has a `run` abstraction that the nixops4 model still lacks - the deployed (trivial) configuration on activation has not facilitated new ssh connections (for subsequent) updates, i.e. a more sophisticated configuration would be needed for real-life usage. Reviewed-on: Fediversity/Fediversity#505
29 lines
734 B
Nix
29 lines
734 B
Nix
{
|
|
inputs = {
|
|
nixops4.follows = "nixops4-nixos/nixops4";
|
|
nixops4-nixos.url = "github:nixops4/nixops4-nixos";
|
|
};
|
|
|
|
outputs =
|
|
inputs:
|
|
import ./mkFlake.nix inputs (
|
|
{ inputs, ... }:
|
|
let
|
|
system = "x86_64-linux";
|
|
in
|
|
{
|
|
imports = [
|
|
inputs.nixops4.modules.flake.default
|
|
];
|
|
|
|
nixops4Deployments.check-deployment-model =
|
|
(import ./deployment/check/common/data-model.nix {
|
|
inherit system inputs;
|
|
config = {
|
|
inherit (import ./deployment/check/data-model-nixops4/constants.nix) pathToRoot pathFromRoot;
|
|
nodeName = "nixops4";
|
|
};
|
|
})."nixops4-deployment".nixops4;
|
|
}
|
|
);
|
|
}
|