Change berglas exec to use sys.Exec? about berglas HOT 6 CLOSED

Hi @thegoodlittlescript

The primary reason it behaves this way is that I had a vision (not implemented) that you could signal the berglas process and it would re-process the secrets (to check for updates) and re-spawn the process if values had changed. I'm not opposed to switching to exec, except I think it doesn't work on Windows?

from berglas.

Hi @sethvargo - I imagine you're right. I wonder however if working on windows should be a goal of this command. Basically I wonder if there should be different commands for the two different platforms.

berglas exec
berglas win-exec

For example, the origin of all this is signal handling but from everything I see signals are not really a windows thing:

• Windows is not POSIX. It does not have signals.
• "Signals are primarily used on Unix-like systems." - golang docs around os.Signal
• ... the internet goes on ...

Maybe that's a hint that exec on windows/unix should be allowed to be different? In my own work I've leaned on unix exec so that I don't have to get into things like signal handling. But honestly I haven't had to design anything cross-platform and I don't know good patterns for it.

from berglas.

I'll look into it.

from berglas.

Let me know if that works for you ^

from berglas.

I built this, deployed it, and have been watching it all day. It seems fine -- the process is still working. Secrets appear to be set as before and as expected there are no more error messages around signals.

Thanks for the quick turnaround! I look forward to seeing this in a future release. Also fwiw I think your design around berglas refs is excellent. Being able to treat secrets like configs has been very helpful. Both our devs and SREs appreciate how visible everything is now.

from berglas.

This issue has been automatically locked since there has not been any
recent activity after it was closed. Please open a new issue for
related bugs.

from berglas.