Repository navigation
Sandbox fleet profile and the onboard-fleet exit rule (ARBORA-FLEET-R085.1) - #779
Merged
Merged
Conversation
…e (R085.1) Adds the declarative sandbox fleet profile, its typed loader, and `onboard-fleet --sandbox`: only the declared connectors are onboarded, and only their failures or a shared infrastructure failure fail the run. Production keeps its current rule. The rollup (R085) stays planned until the connector SDK fixture mode and the sandbox command land. Spec: ARBORA-FLEET-R085.1 Co-Authored-By: Claude Sonnet 5.5 <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.
Adds the declarative sandbox fleet profile (one JSON file, typed loader that refuses a malformed file) and
onboard-fleet --sandbox. In sandbox mode only the declared connectors are onboarded. Only a declared connector failing, or a shared infrastructure step (registry,child-auth), fails the run. A failure outside the set stays in the report and leaves the exit code at zero. Production keeps its current rule and never reads the profile.ARBORA-FLEET-R085 (the rollup) stays planned. It still needs the connector SDK's explicit fixture serving mode (SCION-CONNECTOR-CONTROL-R931, not landed) and the
arbora-sandboxcommand (ARBORA-DEPLOY-R019, not landed). The profile declares names only; each must serve from fixtures once R931 lands.Note: tests/deployment/test_pr_static_scope.py::test_every_source_scanning_test_is_selected fails on main independent of this change (two scanners unlisted).
🤖 Generated with Claude Code