[ENH] Re-enable `QHUB_SECRETS`

[viniciusdc]

We need to re-enable this tooling cited in the docs. Which was originally created to solve #13.

[trallard]

Did we ever consider using sops? I've used it before and it's a pretty decent way to handle secrets.

[viniciusdc]

Did we ever consider using sops? I've used it before and it's a pretty decent way to handle secrets.

Uhm never used that before, looking briefly over their readme seems similar to gopass but with more flexibility. I will have a look, thanks for the suggestion.

just to extend a little the problem here:

• for all cloud providers we are currently importing the necessary credentials from the env vars, and we perform a check here during deployment, so would adopting sops to all secrets affect this as well (?)
• the original reason for QHUB_SECRETS was the ability to pass extra information directly to Terraform wherever it was needed. Within the refactor made in v0.4.0 this might not be a good reason anymore.

Its main purpose right now is just to inform qhub that there is important information to be included in the YAML that needs to be grabbed from env before propagated in the config. The original implementation has more details, so I will link here

[viniciusdc]

But I am really open, and I think the other would be as well, to add something as sops, due to its huge compatibility to a variety of resource (such as Vault)

[trallard]

superseded by #787