Hi, @ashraf1395 ,
Thank you for looking at my question. My cli is 0.243, which is current as of today (3/17/25).
The task definition within resources/dbx_backfill_emotion_job.yml:
tasks:
- task_key: dbx_backfill_base_fields_x_1
# job_cluster_key: job_cluster
python_wheel_task:
package_name: dbx_backfill_emotion
entry_point: main
named_parameters: ¶meter_stub
source_path: x_smpl10_part_*
dbx_schemas_type: base_fields_schema
backfill_date_range: 2024-12-01 UPTO_BUT_EXCLUDING 2025-01-01
target_catalog: ${bundle.environment}_data_warehouse
target_schema: ${workspace.current_user.short_name}
target_table: x_base_fields_backfill_v2_dbxschema
libraries: &library_stub
# By default we just include the .whl file generated for the dbx_backfill_emotion package.
# See https://docs.databricks.com/dev-tools/bundles/library-dependencies.html
# for more information on how to add other libraries.
- whl: ../dist/*.whl
databricks.yml. I am deploying to dev target.
targets:
# The 'dev' target, for development purposes. This target is the default.
dev:
# We use 'mode: development' to indicate this is a personal development copy:
# - Deployed resources get prefixed with '[dev my_user_name]'
# - Any job schedules and triggers are paused by default
# - The 'development' mode is used for Delta Live Tables pipelines
# Your job runs as your service principal so any GCP/AWS permissions need to be assigned to you
mode: development
default: true
resources:
jobs:
dbx_backfill_emotion_job:
run_as:
user_name: ${workspace.current_user.userName}
# Override default settings here.
# tasks:
# - task_key: dbx_backfill_emotion_main
# python_wheel_task:
# named_parameters:
# target_schema: ${workspace.current_user.short_name}
workspace:
host: [redacted]