PowerBI Task DAB deployment fails if table does not exist

[extsteuert]

Describe the issue

When deploying a PowerBI Task the asset bundles validates if the table we plan to push to PowerBI exists. While this check makes sense for incremental workflows for the initial deployment of the job this is not useful since the table first has to be created by the job which is firstly deployed to production.

Configuration

Create a PowerBI task via DAB and reference a table that does not yet exists. If I want to deploy this asset bundle it will fail because the table for the PowerBI Task does not yet exits.

Steps to reproduce the behavior

1. Create a asset bundle definition with a PowerBI Task
2. Reference a Table that does not yet exists.
3. Run databricks bundle deploy

Expected Behavior

Pipeline will be deployed even those table does not yet exists. Since it will be created during the pipline run. Since we have a dbt task running before the PowerBI task.

Actual Behavior

Deployment fails because table does not exist during deployment time but will exist during run time of the pipeline.

OS and CLI version

Windwos
Databricks CLI v0.272.0

Is this a regression?

I don't know tried this the first time.

Debug Logs

Deploying resources...
11:06:06 Debug: Apply pid=12544 mutator=terraform.Apply
Error: terraform apply: exit status 1

Error: cannot update job: 'Run as' user is missing permissions: USE CATALOG on catalog tindp_bi_dev, USE SCHEMA on schema dev_mart or SELECT on table some_insights__obt_viral_alerts

with databricks_job.some_insights__transform_hourly,
on bundle.tf.json line 183, in resource.databricks_job.some_insights__transform_hourly:
183: },

[walthertimmer]

I'm seeing the same. Deployment is succesful if tables already exist from previous run. Even if there's a depends_on in the powerbi action to the job that will create the tables the deployment fails.