Bundle packaging modes + ordered multi-bundle deploy - #41
Closed
matthewmoorcroft wants to merge 2 commits into
Closed
Bundle packaging modes + ordered multi-bundle deploy#41matthewmoorcroft wants to merge 2 commits into
matthewmoorcroft wants to merge 2 commits into
Conversation
matthewmoorcroft
marked this pull request as ready for review
September 1, 2026 12:17
Rewrite internal package-proxy URLs (pypi-proxy.dev.databricks.com) to pypi.org / files.pythonhosted.org so public CI resolves deps. Same pinned versions and hashes; matches main. Co-authored-by: Isaac <no-reply@databricks.com>
Member
Author
|
Closing — this was a port of another author's work and is being withdrawn from the public repo. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements the bundle-packaging design from Greg Hansen's proposal in the classification & single-bundle PR (#39), plus the ordered auto-deploy from Lorenzo Rubio / Alex Nastetsky's follow-up idea.
Relationship to the classification & single-bundle PR
the classification & single-bundle PR (
fix/azure-function-activity-classification) carries the classification + initial single-bundle work and hosts the packaging design discussion. This PR is the packaging implementation, kept as a separate reviewable unit so classification and packaging review independently.Greg's requirements
Must Implement
--packaging-modeflag + adapter promptPACKAGING_MODES = ("per-pipeline", "single", "per-group"); per-group supports both user-specified (--group-by spec) and inferred-from-Run-Pipeline-deps (--group-by inferred)bundler/pipeline_graph.pyDEPLOY.md—bundler/deploy_writer.pyShould Implement
_dedupe_notebooks+_namespace_bundle_artifactswrite_bundle_groupSETUP.mdper bundleOrdered auto-deploy
Per Lorenzo/Alex's follow-up,
bundler/deployer.py(exposed as theflowx-deployskill andadapter deploy) discovers bundles, topologically orders them callees-first, deploys each withdatabricks bundle deploy, reads each deployed job's real numeric id frombundle summary, and injects it into callers via--var— no manual job-id wiring. Verified end-to-end against a live workspace.Testing
test_packaging_modes.py,test_pipeline_graph.py,test_deployer.py,test_deploy_writer.pyNot included here
Two independent packager correctness bugs found while deploy-testing (bare
{{input}}in inner jobs; templatedexisting_cluster_id) are split intofix/foreach-inner-job-packagingsince they're unrelated to packaging design.