Commit Graph

3 Commits

Author SHA1 Message Date
Anton Nekipelov e5f39b5916
Add support for experiments in deployment bind/unbind commands (#2434)
## Changes
1. Changed `FindResourceByConfigKey` to return experiment resources

## Why
This PR adds support for experiment resources in deployment operations,
enabling users to:
- Bind experiments using `databricks bundle deployment bind
<myexperiment_key> <experiment_id>`
- Unbind experiments using `databricks bundle deployment unbind
<myexperiment_key>`

Where:
- `myexperiment_key` is a resource key defined in the bundle's .yml file
- `experiment_id` references an existing experiment in the Databricks
workspace

These capabilities allow for more flexible resource management of
experiments within bundles.

## Tests
Added a new acceptance test that tests bind and unbind methods together
with bundle deployment and destruction.
2025-03-17 15:13:40 +00:00
Anton Nekipelov e2a5953568
Make bind/schema acceptance test run locally (#2463)
## Changes
<!-- Brief summary of your changes that is easy to understand -->
1. Change the cloud acceptance test for `bind/schema` to run locally
2. Add debug lines to the mock server
3. Change `fake_workspace` to create directories for imported files

## Why
<!-- Why are these changes needed? Provide the context that the reviewer
might be missing.
For example, were there any decisions behind the change that are not
reflected in the code itself? -->
1. Local version of the test run can indicate breaking changes faster
than the cloud version and it can be run locally without any predefined
environment variables

## Tests
<!-- How have you tested the changes? -->
1. Ran both acloud and local versions of test, both succeeded

<!-- If your PR needs to be included in the release notes for next
release,
add a separate entry in NEXT_CHANGELOG.md as part of your PR. -->
2025-03-11 12:25:32 +00:00
Anton Nekipelov 0225c77b68
Add acceptance test for binding/unbinding schemas (#2441)
## Changes
<!-- Brief summary of your changes that is easy to understand -->
1. Created a new acceptance test for binding an existing schema to a
bundle
2. Added a feature flag support for acceptance test runner

## Why
<!-- Why are these changes needed? Provide the context that the reviewer
might be missing.
For example, were there any decisions behind the change that are not
reflected in the code itself? -->
1. The test is more simple than an existing integration test for bind
2. The test only can run in environments where Unity Catalog is enabled

## Tests
<!-- How have you tested the changes? -->
New test is passing in CI/CD

## Changelog
NO_CHANGELOG=true
2025-03-07 16:41:25 +00:00