-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Symlink functionality does not seem to work #571
Comments
I've done some testing on my own configuration, and the issue seems to arise when using nested secrets (with a |
Nevermind, nested secrets work fine for me. Back to square 1. |
I've (roughly, see below) copy-pasted the snippet you provided into my own NixOS configuration and I can't reproduce the issue you're having; the files get symlinked fine in my configuration. Not sure what the issue could be... I'd look closer at the rest of your NixOS configuration as the snippet you provided should work fine on its own.
|
I am just starting to use sops-nix (awesome project btw!), this might be my fault:
The symlink functionality does not seem to work for me:
The following snippet contains my config for Syncthing. The Syncthing module thankfully has an option to set the path to the
cert
andkey
, so I was able to fix my issue by using the code below.But with the
path
not commented out (and the other two lines in thesyncthing
block), it didn't work, because no symlinks to the specified directory were made.The secrets were to be found in the
/run/secrets/syncthing
directory, in~/.config/syncthing
there is no file that could "block" the links, the trace shows the right path, and the build does not crash or show any errors, but the symlink is not created.This simple example below does work and the symlink is created in my home directory after rebuild.
It doesn't seem to matter who the owner of the file is or what mode it has. I read through the code but I am no Go wizard so I couldn't figure out why it behaves like this.
Is this maybe Syncthing specific?
The text was updated successfully, but these errors were encountered: