Sensitive configuration values such as passwords, API keys, and tokens. These must be provided as file paths to the secrets, which will be read at activation -time.
Note: If using secret management solutions like agenix or sops-nix with
-home-manager, you need to ensure their services are activated before switching
-to this home-manager generation. Consider setting
-systemd.user.startServices to "sd-switch" for automatic service
-startup.
These values are expanded in a shell context within a systemd service, so +you can use bash features like command substitution or variable expansion +(e.g. “${XDG_RUNTIME_DIR}” as used by agenix).
Type: attribute set of string
@@ -61033,20 +61031,25 @@ attribute set of stringprograms.rclone.writeAfter
+ programs.rclone.requiresUnit
Controls when the rclone configuration is written during Home Manager activation. -You should not need to change this unless you have very specific activation order -requirements.
+The name of a systemd user service that must complete before the rclone +configuration file is written.
This is typically used when secrets are managed by an external provisioner +whose service must run before the secrets are accessible.
When using sops-nix or agenix, this value is set automatically to +sops-nix.service or agenix.service, respectively. Set this manually if you +use a different secret provisioner.
Type: -string
+null or stringDefault:
-"reloadSystemd"
null
+
+Example:
+"agenix.service"
Declared by: