Fabian Jakobs
Fabian Jakobs
Stange. Thanks for the bug report
make sense
sure. I think this is a useful addition
When I move the library out into a library resource then it works just fine: ```hcl resource "databricks_library" "wheel" { cluster_id = databricks_cluster.this.cluster_id whl = databricks_dbfs_file.wheel.dbfs_path } ```
@pietern I don't know what I was thinking :-). The problem is that most dbx commands take the profile from the dbx config, while `dbx sync` ignores it.
@jerrylian-db agreed
With #455 you could do this: `databricks execution-context command-execute-once --cluster-id --command "$(cat metastore-export.py)" --wait`
Just sketching: We could - move the command under the cluster group - make `--wait=True` the default - add an argument that reads the command from a file - add...
We could have different modes. The default could just be informative text based output like I have already implemented: ``` $ python -m databricks_cli.cli execution-context command-execute-once --cluster-id --command "$(cat spark.py)"...
I moved the dev container code out into https://github.com/databricks/databricks-cli/pull/450 and made sure the linter is happy.