v1.0.20 - Let Bundle Handle Cluster Creation and Naming

What's Changed

🐛 Bug Fixes

• Simplified cluster management: Removed manual cluster creation to let bundle handle it properly
• Fixed cluster naming: Bundle should now apply the name from clusters.yml correctly
• Reduced complexity: Eliminated manual cluster detection and creation logic

📋 Technical Details

• Removed manual cluster creation commands from workflow
• Let Warning: unknown field: apps
  at targets.dev.resources
  in databricks.yml:20:7

Warning: unknown field: apps
at resources
in resources/app.yml:2:3

Warning: unknown field: clusters
at resources
in resources/clusters.yml:2:3

Error: cannot resolve bundle auth configuration: validate: more than one authorization method configured: oauth and pat. Config: host=https://ias-dataplatform-dev.cloud.databricks.com/, token=, client_id=your-client-id, client_secret=. Env: DATABRICKS_HOST, DATABRICKS_TOKEN, DATABRICKS_CLIENT_ID, DATABRICKS_CLIENT_SECRET handle cluster lifecycle

• Maintained 120-second wait for cluster readiness
• Kept debugging cluster list for visibility

💡 Why This Should Fix the Naming Issue

The previous approach was creating clusters manually, which bypassed the bundle's cluster configuration. Now:

1. ✅ Bundle creates cluster - Uses the name from
2. ✅ Proper configuration - All settings from the bundle resource are applied
3. ✅ Simplified workflow - Less complexity, fewer failure points
4. ✅ Correct naming - The should now be applied

This release should ensure the cluster is created with the correct name as specified in the bundle configuration.