Open tejas-angelone opened 5 months ago
Having same issue here
In our case we noticed this regression today, we could update the definitions and then update manually on the web, but in our case the number of job clusters is insane and we'll lose too much time.
Unfortunately downgrading to 0.219 in our case doesn't seem to work due to the usage of complex variables.
EDIT: I ended up modifying one by one during 20 minutes all job clusters after adjusting the configuration files.
Describe the issue
The
zone_id
for the job cluster isn't getting updated from thenon-auto
availability zone toauto
AZ. Whereas, the update works fornon-auto
AZs only. So, once a cluster is created withnon-auto
AZ you can switch toauto
.Issue started from CLI
v0.220.0
Steps to reproduce the behavior
zone_id: auto
and deploy the bundleExpected Behavior
zone_id
must update toauto
Actual Behavior
The
zone_id
doesn't get updated fromap-south-1a
(any non-auto AZ) toauto
OS and CLI version
Databricks CLI
v0.220.0
Is this a regression?
Works in Databricks CLI
v0.219.0