Activation fails with "not a directory" if a file becomes a directory

[Ma27]

Suppose you had a secret deployed like this:

{ sops.secrets.foo = {}; }

Now, when deploying a new change with the following secret:

{ sops.secrets."foo/bar" = {}; }

The activation fails like this:

Activation script snippet 'setupSecrets' failed (1)
sops-install-secrets: Imported /etc/ssh/ssh_host_ed25519_key as age key with fingerprint ...
/nix/store/1dilq2rayqd2alchs0bmhssmwni8mbxv-sops-install-secrets-0.0.1/bin/sops-install-secrets: Cannot request units to restart: open /run/secrets/foo/bar: not a directory

[illode]

I also ran into this. Easily fixed by deleting the existing secrets and re-activating the new configuration.

sudo rm -r /run/secrets
sudo /run/current-system/activate