Skip to content

Commit ca3dfbc

Browse files
Merge pull request #130 from duc15052006-dotcom/fix/leftover-database-recovery
feat(desktop): recover from verified leftover database
2 parents 2642af3 + 4f86571 commit ca3dfbc

8 files changed

Lines changed: 1012 additions & 9 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,16 @@ missing, startup stops and asks for the original key instead of creating a repla
2525
make previously encrypted credentials unreadable. The resolved Compose configuration is never
2626
included in diagnostics because it may contain interpolated secrets.
2727

28+
### Desktop can explicitly reset a verified leftover database
29+
30+
When a previous installation's Postgres volume survives but its encryption key is unavailable,
31+
Desktop still refuses to replace that key automatically. A person who does not need the saved data
32+
can now choose a separate destructive recovery path, confirm that the local database will be
33+
permanently deleted, and retry setup fresh. Before removal, OpenBot re-verifies the exact Compose
34+
project, local driver, volume labels, current installation root and original container-engine
35+
connection. External, custom-named, shared, foreign, changed or attached volumes are refused, and
36+
the reset never uses force, prune or stack teardown.
37+
2838
### The EKS cluster recipe blocks Bot pods from the node's IAM role
2939

3040
The EKS example now sets `disableIMDSv1` and `disablePodIMDS` on its managed node group so a Bot's

0 commit comments

Comments
 (0)