databricks-cli/acceptance/bundle/integration_whl/interactive_cluster/script

envsubst < databricks.yml.tmpl > databricks.yml
trace cat databricks.yml
trap "errcode trace '$CLI' bundle destroy --auto-approve" EXIT
trace $CLI bundle deploy
trace $CLI bundle run some_other_job
acc: Simplify integration_whl tests (#2479) ## Changes Instead of full templates, only template databricks.yml and use envsubst for that. 2025-03-14 08:52:20 +00:00			`envsubst < databricks.yml.tmpl > databricks.yml`
acc: Fix interactive_cluster test to use correct config; add NODE_TYPE_ID (#2478) This is a follow up to #2471 where incorrect config was used in interactive_cluster test. ## Changes - Fixed interactive_cluster to use proper config, it was accidentally referring to config from ../base - Add $NODE_TYPE_ID env var and replacement to acceptance tests, this is necessary for interactive_cluster test. - Disable acceptance/bundle/override on cloud. This started failing because it has real node type that gets replaced with NODE_TYPE_ID but only in AWS env. Since the test is focussed on config merging, there is no need to run it against real workspaces. - Modify all tests in integration_whl to print rendered databricks.yml, to prevent this kind of error. 2025-03-12 15:49:24 +00:00			`trace cat databricks.yml`
Convert python_wheel_test.go to acceptance test (#2471) Convert integration/bundle/integration/bundle/python_wheel_test.go to acceptance tests. I plan to expand these tests to check patchwheel functionality. Inside each test there were two runs - with params and without, I've expanded each run into separate test to reduce total time as this runs can be done in parallel. Also add new env var DEFAULT_SPARK_VERSION that matches the one in integration tests. The tests are currently enabled on every PR (`CloudLong=true` is commented out), this can be changed after landing. 2025-03-12 10:51:31 +00:00			`trap "errcode trace '$CLI' bundle destroy --auto-approve" EXIT`
			`trace $CLI bundle deploy`
			`trace $CLI bundle run some_other_job`