[P2] Stale /source/gcloud restic restore path — leftover from GCP #4

New Issue

2026-03-22T18:04:10Z

jeet commented

2026-03-22 18:04:10 +00:00

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

Run restic snapshots to confirm the actual current backup path
Update the hardcoded path, or make it a vault variable:

restic restore latest:{{ restic_restore_path }} --target ./

Files: playbooks/disaster.yml, playbooks/redeploy.yml

## 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`

jeet referenced this issue from a commit

2026-03-22 18:14:21 +00:00

Fix issues 3,5,6,7,8,9,11,15,16: security hardening and reliability improvements

jeet closed this issue

2026-03-22 18:14:33 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: jeet/OCI_Build#4