SECRET_KEY_BASE
env var name auto generates as KEY_BASE #39
Labels
No Label
breaking-change
bug
CI/CD
design
documentation
duplicate
enhancement
help wanted
invalid
plugin
question
secrets
shell-completion
versioning
wontfix
No Milestone
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/abra#39
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
When generating secrets, because
SECRET_
is in the actual app naming of the secret to be generated, this doesnt work, because our logic strips awaySECRET_
and it ends up asKEY_BASE
.I would expect
secret_key_base
to match what the app expects.I would then call it
SECRET_SECRET_KEY_BASE
or justKEY_BASE
but that I can imagine is a bit of a weird work-around that will probably trip people up when they want to use this. Maybe we just need to document it really well. Unsure.export SECRET_SECRET_KEY_BASE_VERSION=v1 # length=30
works for now!SECRET_SECRET_KEY_...
seems silly but not terrible to me.What about documenting this oddness, and coming back to it if'n'when we change the app config format?
Handling this will happen outside of the abra repo so I'll close this off.