Restic does not overwrite existing files at the restore destination by default. If ~/docker has stale configs from a partial previous run, the restore silently leaves the old files in place.
## Problem
Restic does not overwrite existing files at the restore destination by default. If `~/docker` has stale configs from a partial previous run, the restore silently leaves the old files in place.
## Fix
Add the flag to both restore commands:
```yaml
restic restore latest:/source/gcloud --target ./ --overwrite always
```
**Files:** `playbooks/redeploy.yml`, `playbooks/disaster.yml`
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Restic does not overwrite existing files at the restore destination by default. If
~/dockerhas stale configs from a partial previous run, the restore silently leaves the old files in place.Fix
Add the flag to both restore commands:
Files:
playbooks/redeploy.yml,playbooks/disaster.yml