fix: skip in-sandbox provisioning when cloud launcher already seeded ACLs#711
Merged
Conversation
…ACLs The cloud bootstrap sets RELAY_CLOUD_PROVISIONING_DONE=1 to signal that relayfile ACLs were already compiled and seeded by the launcher. Without this guard, the SDK provisioner calls POST /v1/workspaces on the relayfile API — which has no such route — causing a fatal 404 that kills the workflow. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
WorkflowRunner.provisionAgents()whenRELAY_CLOUD_PROVISIONING_DONE=1is setPOST /v1/workspaceson the relayfile API — which has no such route — causing a fatal 404 that kills standalone TS workflowsCompanion PR
bun run)Test plan
agent-relay cloud run— should no longer 404🤖 Generated with Claude Code