experimental/ssh: improve --help copy and surface serverless flags#5156
Open
TanishqDatabricks wants to merge 1 commit intodatabricks:mainfrom
Open
experimental/ssh: improve --help copy and surface serverless flags#5156TanishqDatabricks wants to merge 1 commit intodatabricks:mainfrom
TanishqDatabricks wants to merge 1 commit intodatabricks:mainfrom
Conversation
Updates the help text for `databricks ssh`, `databricks ssh connect`, and `databricks ssh setup` based on the May 1 2026 Remote Development CUJ. - `databricks ssh`: common-workflows examples now lead with serverless (no flags), with the dedicated-cluster path as a follow-up. - `databricks ssh connect`: Long description groups example invocations by serverless vs dedicated. Unhides --name, --accelerator, --ide, --environment-version so users can discover them via --help. - `databricks ssh setup`: tightened Short/Long to clarify it's for dedicated clusters; users on serverless should just use connect. Co-authored-by: Isaac
|
An authorized user can trigger integration tests manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
Waiting for approvalBased on git history, these people are best suited to review:
Eligible reviewers: Suggestions based on git history. See OWNERS for ownership rules. |
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
1 participant
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
databricks ssh: common-workflows examples now lead with serverless (no flags), with the dedicated-cluster path as a follow-up.databricks ssh connect: Long description groups example invocations by serverless vs dedicated. Unhides--name,--accelerator,--ide,--environment-versionso users can discover them via--help.databricks ssh setup: tightened Short/Long to clarify it's for dedicated clusters; users on serverless should just useconnect.CUJ: https://docs.google.com/document/d/1WnIg2vrnPR98cMay8OTY1zJ4yWcKBAHdZUXi5AhYylU/edit?tab=t.7erhv6e67uw#heading=h.kj99al6d2ch
Tracked at DECO-27026 (under epic DECO-27015 FY27Q2 P0 [IDE-Remote] CLI UX).
Test plan
databricks ssh --helpand verify serverless examples appear firstdatabricks ssh connect --helpand verify--name,--accelerator,--ide,--environment-versionare visible (not hidden)databricks ssh setup --helpand verify it references dedicated clusters and points users toconnectfor serverlessThis pull request and its description were written by Isaac.