-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for volumes in deployment bind/unbind commands #2527
Conversation
6248f93
to
8ea8834
Compare
8ea8834
to
7b9719c
Compare
|
||
trace $CLI bundle deployment unbind volume1 | ||
|
||
trace $CLI bundle destroy --auto-approve |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should also be part of trap, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it is part of the test - in the next command we are verifying that an unbound volume is not destroyed when a bundle is
a896715
to
2a487ba
Compare
Changes
FindResourceByConfigKey
to return volume resourcesExists
method on Volume resourceWhy
This PR adds support for volume resources in deployment operations, enabling users to:
databricks bundle deployment bind <myvolume_key> <myvolume_full_name>
databricks bundle deployment unbind <myvolume_key>
Where:
myvolume_key
is a resource key defined in the bundle's .yml filemyvolume_full_name
references an existing volume in the Databricks workspace using its fully qualified (3-level) nameThese capabilities allow for more flexible resource management of volumes within bundles.
Tests
Added a new acceptance test that tests bind and unbind methods together with bundle deployment and destruction.