Skip to content

feat: expose snapshot restore planning API#1023

Closed
nicotsx wants to merge 1 commit into
feat/restore-execution-planningfrom
feat/snapshot-restore-plan-api
Closed

feat: expose snapshot restore planning API#1023
nicotsx wants to merge 1 commit into
feat/restore-execution-planningfrom
feat/snapshot-restore-plan-api

Conversation

@nicotsx

@nicotsx nicotsx commented Jun 30, 2026

Copy link
Copy Markdown
Owner

The restore UI needs a target-scoped answer for the snapshot query root
and whether original-location restore is available. That decision now
belongs to core planning and must account for the selected restore agent
platform

@coderabbitai

coderabbitai Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fc3c8001-bd65-42d3-aa29-d54fe3b8762a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

nicotsx commented Jun 30, 2026

Copy link
Copy Markdown
Owner Author

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

This stack of pull requests is managed by Graphite. Learn more about stacking.

@nicotsx nicotsx force-pushed the feat/restore-execution-planning branch from 45ba516 to b92eaac Compare June 30, 2026 16:51
@nicotsx nicotsx force-pushed the feat/snapshot-restore-plan-api branch 2 times, most recently from a783bab to e5c0ade Compare June 30, 2026 16:55
@nicotsx nicotsx force-pushed the feat/restore-execution-planning branch 2 times, most recently from 389064d to d0c8be1 Compare June 30, 2026 17:11
@nicotsx nicotsx force-pushed the feat/snapshot-restore-plan-api branch from e5c0ade to 7b19d66 Compare June 30, 2026 17:11
@nicotsx nicotsx force-pushed the feat/restore-execution-planning branch from d0c8be1 to b945d28 Compare June 30, 2026 17:22
@nicotsx nicotsx force-pushed the feat/snapshot-restore-plan-api branch from 7b19d66 to 5525cf4 Compare June 30, 2026 17:22
The restore UI needs a target-scoped answer for the snapshot query root
and whether original-location restore is available. That decision now
belongs to core planning and must account for the selected restore agent
platform
@nicotsx nicotsx force-pushed the feat/restore-execution-planning branch from b945d28 to 83050e8 Compare June 30, 2026 18:51
@nicotsx nicotsx force-pushed the feat/snapshot-restore-plan-api branch from 5525cf4 to 5f53fd9 Compare June 30, 2026 18:51
@nicotsx nicotsx closed this Jun 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant