Closed ibozhu closed 5 days ago
Thanks for posting the issue.
This is expected behavior. We check uniqueness because it can lead to ambiguous resource references in the context of bundle run
or bundle summary
. You can work around this by using unique keys.
Describe the issue
It seems like using the same key under different resource types is not supported. For example:
Configuration
Define a job resource like:
Also define a schema resource like:
Steps to reproduce the behavior
Expected Behavior
Same key should be allowed under different resource types
Actual Behavior
Same key is currently not allowed under different resource types
OS and CLI version
Databricks CLI v0.230.0 on MacOS 14.7.1
Is this a regression?
Not sure if it was supported in previous versions or not.
Debug Logs