databricks-cli/bundle/run
shreyas-goenka 41a21af556
Refactor `bundle init` (#2074)
## Summary of changes
This PR introduces three new abstractions: 
1. `Resolver`: Resolves which reader and writer to use for a template.
2. `Writer`: Writes a template project to disk. Prompts the user if
necessary.
3. `Reader`: Reads a template specification from disk, built into the
CLI or from GitHub.

Introducing these abstractions helps decouple reading a template from
writing it. When I tried adding telemetry for the `bundle init` command,
I noticed that the code in `cmd/init.go` was getting convoluted and hard
to test. A future change could have accidentally logged PII when a user
initialised a custom template.

Hedging against that risk is important here because we use a generic
untyped `map<string, string>` representation in the backend to log
telemetry for the `databricks bundle init`. Otherwise, we risk
accidentally breaking our compliance with our centralization
requirements.

### Details

After this PR there are two classes of templates that can be
initialized:
1. A `databricks` template: This could be a builtin template or a
template outside the CLI like mlops-stacks, which is still owned and
managed by Databricks. These templates log their telemetry arguments and
template name.
2. A `custom` template: These are templates created by and managed by
the end user. In these templates we do not log the template name and
args. Instead a generic placeholder string of "custom" is logged in our
telemetry system.

NOTE: The functionality of the `databricks bundle init` command remains
the same after this PR. Only the internal abstractions used are changed.

## Tests
New unit tests. Existing golden and unit tests. Also a fair bit of
manual testing.
2025-01-20 12:09:28 +00:00
..
output Enable perfsprint linter and apply autofix (#2071) 2025-01-07 10:49:23 +00:00
progress Enable perfsprint linter and apply autofix (#2071) 2025-01-07 10:49:23 +00:00
app.go Retry app deployment if there is an active deployment in progress (#2153) 2025-01-15 12:51:06 +01:00
app_test.go Refactor `bundle init` (#2074) 2025-01-20 12:09:28 +00:00
args.go Processing and completion of positional args to bundle run (#1120) 2024-04-22 11:50:13 +00:00
args_test.go Processing and completion of positional args to bundle run (#1120) 2024-04-22 11:50:13 +00:00
job.go Enable perfsprint linter and apply autofix (#2071) 2025-01-07 10:49:23 +00:00
job_args.go Enable gofumpt and goimports in golangci-lint (#1999) 2024-12-12 10:28:42 +01:00
job_args_test.go Processing and completion of positional args to bundle run (#1120) 2024-04-22 11:50:13 +00:00
job_options.go Enable perfsprint linter and apply autofix (#2071) 2025-01-07 10:49:23 +00:00
job_options_test.go Group bundle run flags by job and pipeline types (#1174) 2024-02-06 14:51:02 +00:00
job_test.go Refactor `bundle init` (#2074) 2025-01-20 12:09:28 +00:00
options.go Make sure grouped flags are added to the command flag set (#1180) 2024-02-07 10:27:13 +00:00
pipeline.go Enable perfsprint linter and apply autofix (#2071) 2025-01-07 10:49:23 +00:00
pipeline_options.go Add `--validate-only` flag to run validate-only pipeline update (#1251) 2024-03-04 08:38:32 +00:00
pipeline_options_test.go Add `--validate-only` flag to run validate-only pipeline update (#1251) 2024-03-04 08:38:32 +00:00
pipeline_test.go Refactor `bundle init` (#2074) 2025-01-20 12:09:28 +00:00
runner.go Added support for Databricks Apps in DABs (#1928) 2025-01-13 16:43:48 +00:00
runner_test.go Reuse resource resolution code for the run command (#1858) 2024-10-24 13:24:30 +00:00