From f34755ff3465cb03d3efec33399cd28f499a56a5 Mon Sep 17 00:00:00 2001
From: Eli Ribble <eli@gleipnir.technology>
Date: Fri, 8 May 2026 16:33:28 +0000
Subject: [PATCH] Make restic not fail if we don't configure it

This is relevant for the new quadcore server
---
 modules/system/restic/default.nix | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/modules/system/restic/default.nix b/modules/system/restic/default.nix
index db9034b..c313490 100644
--- a/modules/system/restic/default.nix
+++ b/modules/system/restic/default.nix
@@ -1,13 +1,18 @@
 { pkgs, lib, config, ... }:
 with lib;
-{
+
+let
+	cfg = config.myModules.restic;
+	resticEnabled = cfg.role != null;
+in {
 	# Disable the stable channel version of restic and use our
 	# local copy of the unstable version so that we get access to stdin-from-command
 	disabledModules = [ "services/backup/restic.nix" ];
 	imports = [
 		./restic.nix
 	];
-	config = {
+
+	config = mkIf resticEnabled {
 		sops.secrets.restic-env = {
 			format = "yaml";
 			key = "backblaze-${config.myModules.restic.role}";
@@ -27,6 +32,7 @@ with lib;
 	};
 	options.myModules.restic.role = mkOption {
 		description = "The role which picks the key to use";
-		type = types.str;
+		default = null;
+		type = types.nullOr types.str;
 	};
 }