Repository navigation
Conversation
Serverless environment versions 5 and 6 now work with the tunnel in the regions where the driver's sandbox port forwarding is enabled, so users need a supported way to opt in before the default moves off 4. Make the flag visible, and close the two gaps a public flag would expose: - Fold an explicit version into the default connection name, the same way --base-environment already is. Otherwise `ssh connect` followed by `ssh connect --environment-version 5` reuses the running version 4 server. - Reject the flag together with --cluster instead of silently ignoring it, matching --base-environment and --usage-policy-id. Co-authored-by: Isaac <no-reply@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
Integration test reportCommit: 8c90804
Top 6 slowest tests (at least 2 minutes):
|
| if o.BaseEnvironment != "" && o.ClusterID != "" { | ||
| return errors.New("--base-environment can only be used with serverless compute") | ||
| } | ||
| if o.EnvironmentVersion > 0 && o.ClusterID != "" { |
There was a problem hiding this comment.
Non-blocking: an SSH config entry written by an older CLI from ssh connect --cluster X --environment-version N --ide … has a ProxyCommand with --cluster=X … --environment-version=N (ToProxyCommand appends the version regardless of mode). With this check, that saved ProxyCommand now fails validation on IDE reconnect with "--environment-version can only be used with serverless compute". It only affects people who passed the previously hidden flag with --cluster, the error is clear, and re-running ssh connect rewrites the entry, so probably fine. Mentioning it in case you'd rather ignore the flag in proxy mode for cluster connections instead of rejecting it.
This comment was generated with GitHub MCP.
Changes
ssh connect --environment-versionnow shows in help, with a description that is no longer AI-Runtime-only, and with an example.--base-environmentalready is. Sossh connectfollowed byssh connect --environment-version 5starts a v5 server instead of reusing the running v4 one. Default names without the flag are unchanged.--cluster, matching--base-environmentand--usage-policy-id.Why
CPU serverless environments 5 and 6 now work with the tunnel wherever the REPL sandbox's port forwarding is enabled. That covers SDP stages up to 3am as of 2026-10-29, and I verified it on prod AWS us-west-2 (DECO-28307). Users need a supported opt-in before the default moves off 4 once the rollout finishes. The IDE path already picks up the flag:
ssh connect --ide vscode --environment-version 5carries it in the generated ProxyCommand.ssh setupis dedicated-only, so it gets no flag.Before this change the flag was hidden and ignored with
--cluster, so rejecting that pair can only affect a hand-written invocation that never had any effect.Tests
5).go test ./acceptance -run TestAccept/sshpasses.--helpoutput and the--clusterrejection.This pull request and its description were written by Isaac.