steve/databricks-cli
steve
/
databricks-cli
mirror of https://github.com/databricks/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
databricks-cli/acceptance/bundle/templates/default-sql/output.txt

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

99 lines
2.7 KiB
Plaintext
Raw Normal View History

Add acceptance tests for builtin templates (#2135) ## Changes To accommodate: * Add the server URL to the set of output replacements * Include a call to the permissions API to the dummy server * Run the main script in a subshell to isolate working directory changes
2025-01-14 18:23:34 +00:00
acc: Use [VARNAME] instead of $VARNAME (#2282) $VARNAME is what we use for environment variables, it's good to separate. Some people use envsubst for homemade variable interpolation, it's also good to have separation there.
2025-02-03 14:10:19 +00:00
>>> [CLI] bundle init default-sql --config-file ./input.json --output-dir output
Add acceptance tests for builtin templates (#2135) ## Changes To accommodate: * Add the server URL to the set of output replacements * Include a call to the permissions API to the dummy server * Run the main script in a subshell to isolate working directory changes
2025-01-14 18:23:34 +00:00
Welcome to the default SQL template for Databricks Asset Bundles!
A workspace was selected based on your current profile. For information about how to change this, see https://docs.databricks.com/dev-tools/cli/profiles.html.
acc: Use [VARNAME] instead of $VARNAME (#2282) $VARNAME is what we use for environment variables, it's good to separate. Some people use envsubst for homemade variable interpolation, it's also good to have separation there.
2025-02-03 14:10:19 +00:00
workspace_host: [DATABRICKS_URL]
Add acceptance tests for builtin templates (#2135) ## Changes To accommodate: * Add the server URL to the set of output replacements * Include a call to the permissions API to the dummy server * Run the main script in a subshell to isolate working directory changes
2025-01-14 18:23:34 +00:00
✨ Your new project has been created in the 'my_default_sql' directory!
Please refer to the README.md file for "getting started" instructions.
See also the documentation at https://docs.databricks.com/dev-tools/bundles/index.html.
acc: Use [VARNAME] instead of $VARNAME (#2282) $VARNAME is what we use for environment variables, it's good to separate. Some people use envsubst for homemade variable interpolation, it's also good to have separation there.
2025-02-03 14:10:19 +00:00
>>> [CLI] bundle validate -t dev
Add acceptance tests for builtin templates (#2135) ## Changes To accommodate: * Add the server URL to the set of output replacements * Include a call to the permissions API to the dummy server * Run the main script in a subshell to isolate working directory changes
2025-01-14 18:23:34 +00:00
Name: my_default_sql
Target: dev
Workspace:
acc: Use [VARNAME] instead of $VARNAME (#2282) $VARNAME is what we use for environment variables, it's good to separate. Some people use envsubst for homemade variable interpolation, it's also good to have separation there.
2025-02-03 14:10:19 +00:00
Host: [DATABRICKS_URL]
User: [USERNAME]
Path: /Workspace/Users/[USERNAME]/.bundle/my_default_sql/dev
Add acceptance tests for builtin templates (#2135) ## Changes To accommodate: * Add the server URL to the set of output replacements * Include a call to the permissions API to the dummy server * Run the main script in a subshell to isolate working directory changes
2025-01-14 18:23:34 +00:00
Validation OK!
acc: Use [VARNAME] instead of $VARNAME (#2282) $VARNAME is what we use for environment variables, it's good to separate. Some people use envsubst for homemade variable interpolation, it's also good to have separation there.
2025-02-03 14:10:19 +00:00
>>> [CLI] bundle validate -t prod
Add acceptance tests for builtin templates (#2135) ## Changes To accommodate: * Add the server URL to the set of output replacements * Include a call to the permissions API to the dummy server * Run the main script in a subshell to isolate working directory changes
2025-01-14 18:23:34 +00:00
Name: my_default_sql
Target: prod
Workspace:
acc: Use [VARNAME] instead of $VARNAME (#2282) $VARNAME is what we use for environment variables, it's good to separate. Some people use envsubst for homemade variable interpolation, it's also good to have separation there.
2025-02-03 14:10:19 +00:00
Host: [DATABRICKS_URL]
User: [USERNAME]
Path: /Workspace/Users/[USERNAME]/.bundle/my_default_sql/prod
Add acceptance tests for builtin templates (#2135) ## Changes To accommodate: * Add the server URL to the set of output replacements * Include a call to the permissions API to the dummy server * Run the main script in a subshell to isolate working directory changes
2025-01-14 18:23:34 +00:00
Validation OK!
acc: test "deploy" and "validate -o json" in default-sql
2025-02-10 09:36:11 +00:00
fix default-sql
2025-02-12 10:40:54 +00:00
=== Testing validate
acc: test "deploy" and "validate -o json" in default-sql
2025-02-10 09:36:11 +00:00
>>> [CLI] bundle validate -t dev -o json
>>> [CLI] bundle validate -t prod -o json
>>> diff -u ../../out.validate.dev.json ../../out.validate.prod.json
Exit code: 1
fix default-sql
2025-02-12 10:40:54 +00:00
=== Testing deploy
acc: test "deploy" and "validate -o json" in default-sql
2025-02-10 09:36:11 +00:00
>>> [CLI] bundle deploy -t dev
Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/my_default_sql/dev/files...
Deploying resources...
Updating deployment state...
Deployment complete!
>>> [CLI] bundle deploy -t prod
Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/my_default_sql/prod/files...
update default-sql output
2025-02-10 22:37:25 +00:00
Deploying resources...
Updating deployment state...
Deployment complete!
fix default-sql
2025-02-12 10:40:54 +00:00
=== Testing summary, both JSON and regular output
>>> [CLI] bundle summary -t dev
Name: my_default_sql
Target: dev
Workspace:
Host: [DATABRICKS_URL]
User: [USERNAME]
Path: /Workspace/Users/[USERNAME]/.bundle/my_default_sql/dev
Resources:
Jobs:
my_default_sql_sql_job:
Name: [dev [USERNAME]] my_default_sql_sql_job
update test
2025-02-12 11:28:49 +00:00
URL: [DATABRICKS_URL]/jobs/1?o=900800700600
fix default-sql
2025-02-12 10:40:54 +00:00
>>> [CLI] bundle summary -t dev -o json
>>> [CLI] bundle summary -t prod -o json
>>> [CLI] bundle summary -t prod
Name: my_default_sql
Target: prod
Workspace:
Host: [DATABRICKS_URL]
User: [USERNAME]
Path: /Workspace/Users/[USERNAME]/.bundle/my_default_sql/prod
Resources:
Jobs:
my_default_sql_sql_job:
Name: my_default_sql_sql_job
update test
2025-02-12 11:28:49 +00:00
URL: [DATABRICKS_URL]/jobs/2?o=900800700600
fix default-sql
2025-02-12 10:40:54 +00:00
>>> diff -u ../../out.summary.dev.json ../../out.summary.prod.json
Exit code: 1
acc: test "deploy" and "validate -o json" in default-sql
2025-02-10 09:36:11 +00:00
fix default-sql
2025-02-12 10:40:54 +00:00
=== Testing validate second time, there should be no difference
acc: test "deploy" and "validate -o json" in default-sql
2025-02-10 09:36:11 +00:00
>>> [CLI] bundle validate -t dev -o json
>>> diff -u ../../out.validate.dev.json ../../out.validate.2nd.dev.json
>>> [CLI] bundle validate -t prod -o json
>>> diff -u ../../out.validate.prod.json ../../out.validate.2nd.prod.json