3 Commits

Author	SHA1	Message	Date
Andrew Nester	473d2bf503	Improved error message when 'bricks bundle run' is executed before 'bricks bundle deploy' (#378) ... ## Changes Improved error message when 'bricks bundle run' is executed before 'bricks bundle deploy' The error happens when we attempt to load terraform state when it does not exist. The best way to check if terraform state actually exists is to call `terraform show -json` and that's what already happens here https://github.com/databricks/bricks/compare/main...error-before-deploy#diff-8c50f8c04e568397bc865b7e02d1f4ec5b18379d8d32daddfeb041035d804f5fL28 Absence of `state.Values` indicates that there is no state and likely bundle was just never deployed. ## Tests Ran `bricks bundle run test_job` on a new non-deployed bundle. **Output:** `Error: terraform show: No state. Did you forget to run 'bricks bundle deploy'?` Running `bricks bundle deploy && bricks bundle run test_job` succeeds. --------- Co-authored-by: Pieter Noordhuis <pieter.noordhuis@databricks.com>	2023-05-10 11:02:25 +02:00
Pieter Noordhuis	04e77102c9	Add mutators to pull and push Terraform state (#288) ... ## Changes Pull state before deploying and push state after deploying. Note: the run command was missing mutators to initialize Terraform. This is necessary if the cache directory is removed between running "deploy" and "run" (which is valid now that we synchronize state). ## Tests Manually.	2023-03-30 12:01:09 +02:00
Pieter Noordhuis	b111416fe5	Add `bricks bundle run` command (#134)	2022-12-15 15:12:47 +01:00