-
1. utilizar bcrypt para passwords
2. servidores em utc
3. https only
4. application errors envio para meu email ou algum tracker
5. alertar alguem quando o servico nao tiver rodando
6. load balancing
…
-
## Description
We store our email configuration in the ofn-secrets repository. When provisioning a server, we create `/etc/defaults/openfoodnetwork` to store the email configuration in environm…
-
We see couple of challenges with the current model.
- The users namespace may span multiple clusters and identity management systems.
- The container and host namespaces are decoupled of one ano…
-
The upstream kbs deployment recipes lack explicit state management and store resources like secrets, policies on a local container instance. There are APIs that allow altering of that pod-local state,…
-
**What is the feature request? What problem does it solve?**
Currently, administrators of VDK Control Service configure data jobs using either:
* a configuration type of plugin of VDK SDK
* …
-
**Requester:** Nikhil Kathole
**Issue:** Support for cleaning up more resources on AWS like policies, roles, s3 buckets for AWS from multiple accounts.
**Urgency:** Whenever we can, the existing…
-
# Proposal
It would be nice to have a separate key "variables" to fetch **TF_VAR_** either inline using **env:** for via **envFrom:**. There exists already a similar options for secrets, the "credent…
-
When the user submits the back-up email, it should call recovery code creation. This story is to save the Soledad secret ecrypted with the generated recovery code. However, after this story is done, w…
-
It's generally accepted that keeping secrets on disk in unencrypted files is a _Bad Idea_™. Having secrets inside the fotingo configuration keeps me from publishing it alongside my other dotfiles.
…
-
Using this action, I noticed that environment variables from github secrets are not passed to the server, so they can be used in docker-compose.yml. Or am I mistaken?