Skip to content

fix(harness): honor the session sandbox tier in /v1/runs - #715

Open
moonlight16 wants to merge 1 commit into
rossoctl:mainfrom
moonlight16:fix/runs-sandbox-tier
Open

moonlight16 wants to merge 1 commit into
rossoctl:mainfrom
moonlight16:fix/runs-sandbox-tier

Conversation

@moonlight16

Copy link
Copy Markdown
Member

Summary

POST /v1/runs ignored the session's sandbox tier: knative-server puts sandboxTier in the
config it hands runLeaf, but the prompt, solve and verdict leaves never passed it to
selectPoolSandbox, so every run used the default tier while /v1/turn honored it. This passes
config.sandboxTier as the selection tier in all three leaves. A session with no tier is
unchanged. A microVM-tier run that names a workload now fails with workload_sandbox_unavailable
instead of silently running in the container tier, since workload sandboxes are container-only.

Checklist

  • Commits are signed off (git commit -s).
  • make lint and the tests for the touched packages pass.
  • Docs: changed behavior, flags or environment variables are reflected in the relevant README or
    docs/ page, with the right maturity label (see docs/CONTRIBUTING-DOCS.md). (n/a: bug fix)
  • Docs: make check-links passes if any Markdown changed. (n/a)
  • A new spec or ADR is registered in docs/specs/README.md or docs/adrs/README.md. (n/a)

Signed-off-by: Jeremy Cohn <Jeremy.Cohn@ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant