Repository navigation
spice-cloud-management: fork projects through the Management API - #22
Merged
Merged
Conversation
Document POST /v1/projects/{projectId}/forks and GET
/v1/projects/{projectId}/forks: fields, what a fork copies, the
shared_state check before its first deployment, error codes, and
forked_from on project responses. Add a workflow to copy or move a
project to another region, fork-project and list-forks helper commands,
and an eval.
lukekim
marked this pull request as ready for review
September 30, 2026 18:21
Resolve CHANGELOG.md and skills/cloud/SKILL.md after the spice-cloud-management → cloud rename. Keep project-fork docs (compact in SKILL.md, details in references/project-forks.md) under the 500-line skill budget.
Resolve the CHANGELOG.md conflict by keeping both Unreleased entries: project forks for cloud and the new launch skill.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Teaches
spice-cloud-managementto fork Spice.ai Cloud projects through the Management API. The endpoints come from spicehq/cloud#5856, which depends on the migration in spicehq/cloud#5855.Note
Keep this in draft until spicehq/cloud#5856 is deployed. Before then,
POST /v1/projects/{projectId}/forksdoes not exist and agents following the skill would get a 404. The section is dated(Sep 2026)following the changelog-month convention; update it if the API ships later.Changes
SKILL.mdPOSTandGET /v1/projects/{projectId}/forks.name,region,cluster_name,scheduler_state_location)shared_statecheck before its first deploymentforked_fromon project responsesfork_placement_required,scheduler_state_location_*,fork_name_unavailable,fork_source_has_no_spicepod/fork_source_spicepod_invalid,fork_source_loads_repository_files, andfork_source_repository_unreadable.scripts/spice-cloud.sh:fork-project <projectId> [name] [region]andlist-forks <projectId>.evals/evals.json: eval 3 asks for a copy of a project in another region. It checks that the answer forks the project rather than recreating it, targets the region, readsshared_state, and deploys the fork.CHANGELOG.md: an Unreleased entry.Testing
bash -n scripts/spice-cloud.shpasses, and the new commands appear in the usage text.evals.jsonparses. The new regexes pass on sample answers that use curl and ones that use the helper script, and fail on an answer that recreates the project by hand.SKILL.mdis 498 lines, under the 500-line limit.make check-versionsalready fails ontrunkfor every skill ("not checked against v2.3.2" after the 2.3.2 release). This PR does not change that.