refactor!: rename the remote command group to cloud - #261
Draft
outofcoffee wants to merge 3 commits into
Draft
outofcoffee wants to merge 3 commits into
outofcoffee wants to merge 3 commits into
Conversation
added 2 commits
October 5, 2026 23:15
Rename `spinloop remote` to `spinloop cloud`, the fleet node kind `remote` to `cloud`, `SPINLOOP_REMOTE_*` to `SPINLOOP_CLOUD_*`, and the on-disk `remotes/<name>/remote.json` and `remote-<region>.json` to `clouds/<name>/cloud.json` and `cloud-<region>.json`. `internal/remote` becomes `internal/cloud`. The old names are removed with no fallback: registered environments must be re-registered with `spinloop cloud deploy`. The `remote/` CDK project and URL-sourced Spinloops keep their names. Refs #117
outofcoffee
force-pushed
the
worktree-remote-to-cloud-rename
branch
from
October 5, 2026 22:19
49df962 to
602422e
Compare
This branch has not been deployed
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.
Renames
spinloop remotetospinloop cloud, along with the fleet node kind, environment variables and on-disk names that go with it.Summary
spinloop remote …is nowspinloop cloud …; subcommands are unchanged.kind: cloud.SPINLOOP_REMOTE_*is nowSPINLOOP_CLOUD_*.clouds/<name>/cloud.json; keystore files arecloud-<region>.json.internal/remoteis nowinternal/cloud, and the fleet node, files, tests, help text, docs, examples and specs follow.remoteis an unknown command,kind: remoteis rejected,SPINLOOP_REMOTE_*is ignored, and environments registered underremotes/must be re-registered withspinloop cloud deploy.Implementation details
remote/CDK project keeps its name: the bootstrap download, CI andscripts/check-no-cloud-identifiers.shrefer to it, and renaming it changes the release layout for no user-visible gain.remote-spinloop-sources) keep their name. They mean "fetched over HTTP", which is a different thing.openspec/specs/directory names are unchanged; their wording is updated. The naming contract is in the newcloud-commandcapability, in the OpenSpec changerename-remote-to-cloud, which needs archiving before merge.REMOTEreferences are tracked separately in chore: remove the leftover path-form REMOTE references #259.Closes #117