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
Hi @dssdss, sorry for our late response. thank you for notifying us of this issue! We will try and reproduce this sometime in the coming weeks, and come back to you regarding ths.
Remote development over SSH: https://code.visualstudio.com/docs/remote/ssh-tutorial
https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-ssh
I've added the SOPS_AGE_KEY_FILE and SOPS_AGE_KEY to my ~/.bashrc
Environment Variables
export SOPS_AGE_KEY_FILE=$HOME/.config/sops/age/keys.txt
export SOPS_AGE_KEY=age102mszwln8mqkshl3shjn0ytr2pjqnsnepka5j90wu5mnlgluasfsks4kgn
I've created a .sops.yaml
creation_rules:
age: age102mszwln8mqkshl3shjn0ytr2pjqnsnepka5j90wu5mnlgluasfsks4kgn
I've even created a .sopsrc
ageKeyFile: $HOME/.config/sops/age/keys.txt
I know sops works because I can use sops --encrypt --in-place file.env to encrypt and sops --decrypt --in-place file.env to decrypt it.
But in VSCode, even when I open file with "SOPS: edit directly" - VSCode only open encrypted file!
The text was updated successfully, but these errors were encountered: