mirror of https://github.com/databricks/cli.git
## Changes This adds `mode: production` option. This mode doesn't do any transformations but verifies that an environment is configured correctly for production: ``` environments: prod: mode: production # paths should not be scoped to a user (unless a service principal is used) root_path: /Shared/non_user_path/... # run_as and permissions should be set at the resource level (or at the top level when that is implemented) run_as: user_name: Alice permissions: - level: CAN_MANAGE user_name: Alice ``` Additionally, this extends the existing `mode: development` option, * now prefixing deployed assets with `[dev your.user]` instead of just `[dev`] * validating that development deployments _are_ scoped to a user ## Related https://github.com/databricks/cli/pull/578/files (in draft) ## Tests Manual testing to validate the experience, error messages, and functionality with all resource types. Automated unit tests. --------- Co-authored-by: Fabian Jakobs <fabian.jakobs@databricks.com> |
||
---|---|---|
.. | ||
autoload_git | ||
basic | ||
bundle | ||
conflicting_resource_ids | ||
environment_empty | ||
environment_overrides | ||
include_default | ||
include_invalid | ||
include_multiple | ||
include_with_glob | ||
interpolation | ||
job_and_pipeline | ||
variables | ||
yaml_anchors | ||
README.md | ||
autoload_git_test.go | ||
basic_test.go | ||
conflicting_resource_ids_test.go | ||
environment_empty_test.go | ||
environment_overrides_test.go | ||
include_test.go | ||
interpolation_test.go | ||
job_and_pipeline_test.go | ||
loader.go | ||
variables_test.go | ||
yaml_anchors_test.go |
README.md
Bundle configuration tests
Every test here uses an example bundle configuration. Each bundle configuration is located in a dedicated subdirectory.