This path is a leftover from when the stack ran on Google Cloud. If backups are now snapshotted under a different path on OCI, the restore either pulls stale data or silently restores nothing.
Fix
Run restic snapshots to confirm the actual current backup path
Update the hardcoded path, or make it a vault variable:
## Problem
```
restic restore latest:/source/gcloud --target ./
```
This path is a leftover from when the stack ran on Google Cloud. If backups are now snapshotted under a different path on OCI, the restore either pulls stale data or silently restores nothing.
## Fix
1. Run `restic snapshots` to confirm the actual current backup path
2. Update the hardcoded path, or make it a vault variable:
```yaml
restic restore latest:{{ restic_restore_path }} --target ./
```
**Files:** `playbooks/disaster.yml`, `playbooks/redeploy.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
This path is a leftover from when the stack ran on Google Cloud. If backups are now snapshotted under a different path on OCI, the restore either pulls stale data or silently restores nothing.
Fix
restic snapshotsto confirm the actual current backup pathFiles:
playbooks/disaster.yml,playbooks/redeploy.yml