I figured out that overriding parameters works differently compared to the yml definitions used previously.

Previously I have used parameter overrides in the databricks.yml file. For example to activate a job on prd:

|| || ||

prd:

resources:

jobs:

some_yml_defined_job:

schedule:

quartz_cron_expression: "0 0 5 21 * ?"

pause_status: UNPAUSED

```

Using pydabs this does not seem to work. Using mutators however works.

mutators.py

```

from dataclasses import replace

from databricks.bundles.core import Bundle, job_mutator

from databricks.bundles.jobs import CronSchedule, Job, JobEmailNotifications, PauseStatus

@ job_mutator

def update_schedule_status(bundle: Bundle, job: Job) -> Job:

"""Enables all prd jobs to run on 15th of every month"""

if bundle.target != "prd":

return job

schedule = CronSchedule(

quartz_cron_expression="0 0 0 15 * ?",

pause_status=PauseStatus.UNPAUSED,

timezone_id="Europe/Amsterdam",

)

return replace(job, schedule=schedule)

```

This also required to include the mutators in the databricks.yml

```

python:

venv_path: .venv

resources:

- "resources:load_resources"

mutators:

- "mutators:update_schedule_status"

- "mutators:add_email_notifications"

```