[ISSUE] Issue with databricks_workspace_file
resource
#4672
Labels
Triaged
The issue has been reviewed. Issues without a “Triaged” label require triage/review.
Configuration
# We are using Databricks Asset bundle to deploy the jobs
Expected Behavior
Deployment should be completed
Actual Behavior
2025-04-24 15:47:49 + databricks bundle deploy -t sandbox --var=suffix=dacci-143
2025-04-24 15:47:50 Building default...
2025-04-24 15:47:51 Uploading consumer_campaign_intelligence-0.1.0-py3-none-any.whl...
2025-04-24 15:47:51 Uploading bundle files to /Workspace/Users/0b66cdac-04f8-408e-9290-13c058a2ebe1/automated_product_tagging/dacci-143/files...
2025-04-24 15:48:06 Deploying resources...
2025-04-24 15:48:06 Updating deployment state...
2025-04-24 15:48:06 Deployment complete!
Error: terraform apply: exit status 1
2025-04-24 15:48:06
2025-04-24 15:48:06 Error: Provider produced inconsistent final plan
2025-04-24 15:48:06
2025-04-24 15:48:06 When expanding the plan for databricks_job.data_preprocessing to include new
2025-04-24 15:48:06 values learned so far during apply, provider
2025-04-24 15:48:06 "registry.terraform.io/databricks/databricks" produced an invalid new value
2025-04-24 15:48:06 for .parameter[4].default: was
2025-04-24 15:48:06 cty.StringVal("/Workspace/Users/0b66cdac-04f8-408e-9290-13c058a2ebe1/automated_product_tagging/dacci-143/[dacci-143
2025-04-24 15:48:06 ds_digital_foc_service_user_dev] ds-digital-cci-crmx_data_preprocessing"),
2025-04-24 15:48:06 but now
2025-04-24 15:48:06 cty.StringVal("/Users/0b66cdac-04f8-408e-9290-13c058a2ebe1/automated_product_tagging/dacci-143/[dacci-143
2025-04-24 15:48:06 ds_digital_foc_service_user_dev] ds-digital-cci-crmx_data_preprocessing").
2025-04-24 15:48:06
2025-04-24 15:48:06 This is a bug in the provider, which should be reported in the provider's own
2025-04-24 15:48:06 issue tracker.
2025-04-24 15:48:06
2025-04-24 15:48:06 Error: Provider produced inconsistent final plan
Steps to Reproduce
Important Factoids
Would you like to implement a fix?
Suggest a fix
The text was updated successfully, but these errors were encountered: