mirror of https://github.com/databricks/cli.git
6feaed4990
## Changes Consider the following host based configuration: ``` bundle: name: job_with_file_task workspace: host: https://e2-dogfood.staging.cloud.databricks.com/ ``` If you have a DEFAULT profile, then this host is ignored. The solution proposed here is to remove the profile config loader if host is explicitly specified in the bundle config. This does come with a cost, namely that if a `DATABRICKS_CONFIG_PROFILE` env var will be ignored, which maybe goes against unified auth spec The ideal solution here is probably to make a change to go-SDK to not select DEFAULT profile if host is not empty ## Tests <!-- How is this tested? --> |
||
|---|---|---|
| .. | ||
| artifacts | ||
| config | ||
| deploy | ||
| deployer | ||
| internal/tf | ||
| phases | ||
| run | ||
| schema | ||
| tests | ||
| bundle.go | ||
| bundle_test.go | ||
| context.go | ||
| context_test.go | ||
| mutator.go | ||
| mutator_test.go | ||
| root.go | ||
| root_test.go | ||