Changing stack name doesn't also change secrets on undeploy/deploy #405
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#405
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?
You deploy foo_example_com. You generate secrets. Later, you rename to
example_com
. via hacking theDOMAIN=...
or simply renaming the.env
file. All the secrets still havefoo_example_com
in their naming. We can't retrieve the secrets, so delete/re-create wouldn't work? Couldabra
do some sort of duplication of secrets to help this scenario?To me
abra app rename
would be the answer, then we strongly recommend against manually renaming the.env
file or settingSTACK_NAME
.rename
knows both the old and the new name (as CLI args) so it should be chill to copy over the data.