Skip to content

Commit 833336a

Browse files
committed
docs: fix clone howto issues from deep review
- destroy-clone: remove incorrect create-clone screenshot reference - reset-clone: add --async flag example https://claude.ai/code/session_011sPDgBjzL2N2X6jiYyoTjQ
1 parent ef92ee0 commit 833336a

File tree

2 files changed

+5
-1
lines changed

2 files changed

+5
-1
lines changed

docs/dblab-howtos/cloning/destroy-clone.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,6 @@ A protected clone cannot be deleted automatically or manually. To delete it, fir
1313

1414
## GUI
1515
1. On the **Database Lab clone** page click the **Destroy** button.
16-
![DBLab Engine page / Create clone](/assets/guides/create-clone-1.png)
1716
1. Accept confirmation dialog and wait for it. You will be redirected to the **Database Lab instance** page.
1817

1918
## CLI

docs/dblab-howtos/cloning/reset-clone.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,5 +44,10 @@ dblab clone reset --snapshot-id SNAPSHOT_ID CLONE_ID
4444
The parameters `--latest` and `--snapshot-id` must not be specified at the same time.
4545
:::
4646

47+
For long-running operations, use the `--async` flag:
48+
```bash
49+
dblab clone reset --async --latest CLONE_ID
50+
```
51+
4752
## Related
4853
- Guide: [Destroy a clone](/docs/dblab-howtos/cloning/destroy-clone)

0 commit comments

Comments
 (0)