Skip to content

feat: make apps init interactive by default, simplify flow#4879

Open
jamesbroadhead wants to merge 1 commit intodatabricks:mainfrom
jamesbroadhead:jb/apps-init-interactive-flow
Open

feat: make apps init interactive by default, simplify flow#4879
jamesbroadhead wants to merge 1 commit intodatabricks:mainfrom
jamesbroadhead:jb/apps-init-interactive-flow

Conversation

@jamesbroadhead
Copy link
Copy Markdown

Summary

  • Add --interactive flag (default true) replacing implicit flags-mode. --name and --deploy now pre-fill values while still showing prompts. Use --interactive=false for fully non-interactive mode.
  • Remove the description prompt from interactive flow (--description flag still works).
  • Auto-fill lakebase database branch with "production" instead of prompting.
  • Don't auto-run the app after creation; always print the next-steps command. Deprecate --run flag.
  • Generate a default project name (my-app, my-app-1, etc.) when --interactive=false and --name not provided.

Test plan

  • All existing tests pass (go test ./cmd/apps/ ./libs/apps/prompt/)
  • New tests for --interactive flag default, generateProjectName with suffix bumping
  • Manual test: databricks apps init shows interactive prompts
  • Manual test: databricks apps init --name foo shows interactive prompts with name pre-filled
  • Manual test: databricks apps init --interactive=false generates project with defaults

This pull request was AI-assisted by Isaac.

- Add --interactive flag (default true) replacing implicit flagsMode.
  Passing --name or --deploy now pre-fills values while still showing
  prompts. Use --interactive=false to skip all prompts.
- Remove the description prompt from the interactive flow (--description
  flag still works for explicit use).
- Auto-fill lakebase database branch with "production" instead of
  prompting.
- Don't auto-run the app after creation; always print the next-steps
  command instead.
- Generate a default project name ("my-app", "my-app-1", etc.) when
  --interactive=false and --name is not provided.

Co-authored-by: Isaac
@jamesbroadhead jamesbroadhead requested a review from a team as a code owner March 31, 2026 16:42
@github-actions
Copy link
Copy Markdown

An authorized user can trigger integration tests manually by following the instructions below:

Trigger:
go/deco-tests-run/cli

Inputs:

  • PR number: 4879
  • Commit SHA: c7a92afe4da27755ec93ef2f71815bcdc41a3ba2

Checks will be approved automatically on success.

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