is chaining Consumers a thinkable reality?

Originally posted by @krysopath in #1 (comment)

yes, this issue encapsulates the ChainConsumer idea and implementation

should be able to pull a private key from vault and use paramiko to establish some kind of ssh session with a host

for this to work smoothly the looping over dir part of the providers should be deduplicated and performed by the Vaultify class before handing it over to the Consumer

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.

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

so either or:

• typed values user dict
• cerberus