generate secrets from config #356
Reference in New Issue
Block a user
No description provided.
Delete Branch "fix-secret-generation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We won't read the
.envfile for secret names anymore, we'll read them from the recipe config. This is more consistent as pointed out in coop-cloud/organising#464. Here's what still needs implementing:.envof the app, not the.env.sample.envof the app & it is in the recipe config, warn we can't generateCOMPOSE_FILEso we don't generate unwanted secrets3d2e307892tod49bf7735dd49bf7735dtoc065ceb1f0WIP: generate secrets from configto generate secrets from config