"abra app restore" reports sucess when no 'backupbot.restore: "true"' present #430
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
Also, if there are no pre/post-hooks defined then the database usually isn't being re-imported! So, we should probably warn for that case on restore. Otherwise it's all just a bit confusing. It says it worked but it did nothing 😆
@3wordchant looked into this, actually, if you run say:
And there is no
backup.restore=true
, thenabra
will restorefoo.txt
to/tmp/
on the container. It will not run any definedpre-hook/post-hook
defined labels (cus that code checks forbackup.restore=true
first).This is confusing right now but I guess more convenient? You can arbitrarily restore
*.tar.gz
files to a container without first definingbackup.restore=true
on the recipe configuration.Do we want to lock that down and error out if
backup.restore=true
is not found?Controlled by
backup-bot-two
now 🙈