You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a case where a program needs to modify the secrets.
So the existing workflow is to make the program behave like an editor, and execute sops like:
EDITOR=path/to/tool sops path/to/encrypted_secret
This approach works for most of the case, however, we cannot pass arguments to the tool unless using a wrapper script for the conversion.
On the other hand, exec-file mode provides a much better interface for interacting with external tools. Which even uses FIFO device to avoid putting the secret on disk. It would be nice to make the FIFO bi-directional, so that the program could optionally write the modified content back to the device.
We have a case where a program needs to modify the secrets.
So the existing workflow is to make the program behave like an editor, and execute sops like:
This approach works for most of the case, however, we cannot pass arguments to the tool unless using a wrapper script for the conversion.
On the other hand, exec-file mode provides a much better interface for interacting with external tools. Which even uses FIFO device to avoid putting the secret on disk. It would be nice to make the FIFO bi-directional, so that the program could optionally write the modified content back to the device.
The text was updated successfully, but these errors were encountered: