Skip to content

[factory:bug-fixer][custom-training] Suggest how to regenerate a matching AIR workload bundle - #7835

Draft
ben-hansen-db wants to merge 3 commits into
mainfrom
ben.hansen/rf-cnxt-2668-20261120
Draft

ben-hansen-db wants to merge 3 commits into
mainfrom
ben.hansen/rf-cnxt-2668-20261120

Conversation

@ben-hansen-db

Copy link
Copy Markdown
Contributor

Changes

When local code sits outside the bundle directory, air convert-to-dabs now suggests --output-dir <parent> --force if the parent contains a single databricks.yml whose literal bundle name matches the workload. The user must run the suggested command to replace the bundle.

Why

After generating a bundle in the suggested parent, rerunning the original command told users to choose another directory even when they wanted to regenerate the same workload.

Tests

Added a command-level regression covering regeneration, mismatched or missing names, malformed YAML, and alternate or duplicate bundle files. The regression passed 50 consecutive runs. The native test suite, formatting, checks, and lint passed.

This PR was written by Codex.

@github-actions github-actions Bot added the AIR Databricks AI Runtime CLI label Nov 20, 2026
@eng-dev-ecosystem-bot

Copy link
Copy Markdown
Collaborator

✅ Integration test report

Commit: b3b2312

Run: 44670423839

Env ✅​pass 🙈​skip Time
✅​ aws linux-2core-8gb 273 19 4:09
✅​ aws-windows-latest-4core-16gb 275 17 4:00
✅​ azure linux-2core-8gb 272 19 4:17
✅​ azure-windows-latest-4core-16gb 274 17 4:23
✅​ gcp linux-2core-8gb 273 19 4:36
✅​ gcp-windows-latest-4core-16gb 275 17 4:40
Top 4 slowest tests (at least 2 minutes):
duration env testname
4:35 gcp-windows-latest-4core-16gb TestAccept
4:22 azure-windows-latest-4core-16gb TestAccept
3:57 aws-windows-latest-4core-16gb TestAccept
2:02 azure linux-2core-8gb TestAccept

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AIR Databricks AI Runtime CLI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants