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
add PlainTextProvider and OpenSSLConsumer as well as GPGConsumer, where the first just reads from plaintext dotenv and the latter create an encrypted version of the vaultify Kn=Vn dotenv file.
this avoids failures due to different implementations of openssl and gpg when using docker.
krysopath
changed the title
add PlainTextProvider and OpenSSLConsumer as well as GPGConsumer, where the first just reads from plaintext dotenv and the latter create an encrypted version of the vaultify Kn=Vn dotenv file.
add PlainTextProvider,OpenSSLConsumer, GPGConsumer`
Apr 17, 2019
krysopath
changed the title
add PlainTextProvider,OpenSSLConsumer, GPGConsumer`
add PlainTextProvider, OpenSSLConsumer, GPGConsumer
Apr 17, 2019
add
PlainTextProvider
andOpenSSLConsumer
as well asGPGConsumer
, where the first just reads from plaintext dotenv and the latter create an encrypted version of the vaultifyKn=Vn
dotenv file.this avoids failures due to different implementations of openssl and gpg when using docker.
Originally posted by @krysopath in #1 (comment)
create a viable pattern for creation of encrypted configuration files to avoid hassle when the vaultify binaries are different from the creators host
The text was updated successfully, but these errors were encountered: