generate secrets from config #356
No reviewers
Labels
No Label
bug
build
ci/cd
contributing
design
documentation
duplicate
enhancement
help wanted
invalid
meta
question
security
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/abra#356
Loading…
Reference in New Issue
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
.env
file 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:.env
of the app, not the.env.sample
.env
of the app & it is in the recipe config, warn we can't generateCOMPOSE_FILE
so we don't generate unwanted secrets3d2e307892
tod49bf7735d
d49bf7735d
toc065ceb1f0
WIP: generate secrets from configto generate secrets from config