Repository navigation
feat: --stack-start=manual holds submitted stacks until started from the UI - #73
Merged
Merged
Conversation
…the UI
Adds a startup option to control whether submitted stacks start straight away:
nebula --http=8099 --stack-start=manual (or NEBULA_STACK_START=manual)
- auto (default): unchanged - stacks start as soon as they're submitted.
- manual: stacks are held as NotStarted until started from the management UI
(or POST /api/stacks/{id}/start). A resubmission still replaces the stack,
and the replacement waits too. Ignored when running a script, where there's
no UI to start it from.
A held stack is wired to its event and log streams on submission, so
consumers (eg: Orbital) see it as NotStarted and receive its coordinates once
it starts. Previously that wiring only happened on the initial start path, so
starting a never-started stack would have left consumers without updates.
startStack/startComponent now also refresh the state reported by GET /stacks.
The UI shows these stacks as "Not started", with a Start action.
Also stops logging the full payload of each /stream/stacks submission (every
script in it) - it now logs a single line naming the submitted stacks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅ Deploy Preview for orbital-nebula ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
# Conflicts: # nebula-ui/src/pages/stack-detail/ComponentsView.tsx
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
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
Adds a startup option that controls whether submitted stacks start straight away:
nebula --http=8099 --stack-start=manual # or NEBULA_STACK_START=manual nebula --http=8099auto(default): no change. Stacks start as soon as they're submitted.manual:POST /api/stacks/{id}/start.--http. When running a script there's no UI to start the stack from, so Nebula warns and starts it straight away.Also, submissions over
/stream/stacksno longer log the whole payload, which contained every script in the submission. It now logs one line naming the stacks, e.g.Received submission of 8 stack(s): orbital1/..., org2/....Details
NotStartedand gets its connection details once it starts. Without this, starting a never-started stack from the UI would have left Orbital with no updates.startStackandstartComponentnow refresh the component info returned byGET /stacks. Previously only the first start set it.docs/pages/cli.mdxgets the option in the options table and a "Starting stacks manually" section with CLI, env-var and docker-compose examples.CLAUDE.mdandnebula-ui/README.mdget short mentions.Test plan
StackStartModeTest(new):NotStarted, thenRunningonce started, and fills inGET /stacksautomode is unchangedStackRunnerResubmissionTest,StackStartFailureTest,NebulaServerTest,StreamStacks*,UpdateStackRequestCompatibilityTestNEBULA_STACK_START=manual:🤖 Generated with Claude Code