検索

Scott Williams 🐧@[email protected]2024-01-11 01:24

public

Updated our #Infisical to an enterprise license today and migrated the folder path structure in Hashicorp Vault kv2 engines using the CLIs and a bit of python and ses magic to reparse it all. Hoping to complete the migration and get everyone in the pool tomorrow. 💪

Scott Williams 🐧@[email protected]2024-01-05 01:32

public

Very close to fully replacing Hashicorp Vault with #Infisical at work. If you primarily use the kv2 store in Vault, Infisical is a good alternative.

Scott Williams 🐧@[email protected]2023-09-11 21:48

public

返信元:

Scott Williams 🐧@[email protected]2023-09-11 19:14

public

Idea: An #opensource #secrets manager, with a fancy web UI like #Hashicorp #Vault, that can organize secrets by folders and deployment target (dev, staging, prod) and the CLI tool can translate those folders, keys, and values into *structured* YAML or JSON output in addition to environment variables. Additionally, it can *import* secrets into new projects with structure YAML/JSON into the format. Something like this for the data backend: https://github.com/smithjm/etcd-export

I half sort of found a way to do this with #Infisical and #yq, by using props annotation and parsing it through yq:

infisical export --env=dev -fyaml | yq -pprops -o yaml

This get it's into properly formatted yaml. yq can also do the same in the opposite direction to import back into infisical.

And to support having .'s in keys, use \\x2e and pass it through echo:

echo -e "$(infisical export --env=dev -fyaml | yq -pprops -o yaml)"

Scott Williams 🐧@[email protected]2023-09-05 19:42

public

返信元:

Scott Williams 🐧@[email protected]2023-09-05 19:38

public

I'm starting to wonder if this is intentional to make it harder or impossible to do this with helm, since the "community" version of this fully open source project has a hard-coded disable for upgrades, and well, having a helm chart provides an upgrade path for something that #EnvKey seems to be attempting to paywall.

This unfortunately has the opposite effect than they are probably wishing it has, in that I'm less likely to continue to want use the paid EnvKey, or EnvKey at all.

So, given these shenanigans, the reason to consider #EnvKey over #Infisical is that EnvKey is, on-paper, fully FOSS where Infisical is "open core". But Infisical has no problem with you shipping their "community" version with a helm chart. They even provide one! https://infisical.com/docs/self-hosting/deployment-options/kubernetes-helm

I'm all for adopting a FOSS project that *almost* meets my needs and making it better until it does, but seeing EnvKey do some apparent self-sabotage really turns me off from wanting to contribute to it.