Got stacktrace probably correlated with unencrypted editor is not properly replaced with encrypted at save. about intellij-sops-plugin HOT 6 CLOSED

After testing, everything looks good to me, and it cant be more broken then the current implementation. So im gonna ship it 🚢

Let me know if your issue is not resolved by this release. As i said, keep in mind that some files may still cause issues if you dont fix the permissions manually.

from intellij-sops-plugin.

Because i made the file read-only i am blocking myself from writing the updated secrets. I am confused how i managed to overlook this issue while testing it...

Working on a fix now!

from intellij-sops-plugin.

I think i got it. I created a draft release with the fix.

Again sorry for missing this in the first place, gonna test this one a bit more thoroughly before release.

EDIT: You may need to clear the read-only status of the affected files manually to get everything to work correctly again. (chmod -R ...)

from intellij-sops-plugin.

That is what happens :) Much rather have a few quick fixes than cathedral building that drags on for centuries :)

from intellij-sops-plugin.

Is there a way to tell the IntelliJ cache system that this file is read/only instead of changing the file attributes underneath?

from intellij-sops-plugin.

That is more or less what i did in this change. Instead of setting the read-only flag on the actual file i just mark the "opened instance" of it as read-only.

from intellij-sops-plugin.