Repository navigation
Add non-DAG bundle deploys - #166
Merged
Merged
Conversation
jeremybeard
added this pull request to stack #169
October 15, 2026 17:25
jeremybeard
force-pushed
the
non-dag-bundles
branch
from
October 15, 2026 19:03
c2467f2 to
f114bb6
Compare
jeremybeard
force-pushed
the
non-dag-bundles
branch
from
October 15, 2026 19:30
f114bb6 to
889e75e
Compare
jeremybeard
force-pushed
the
non-dag-bundles
branch
from
October 16, 2026 17:59
889e75e to
efce798
Compare
jeremybeard
force-pushed
the
non-dag-bundles
branch
2 times, most recently
from
October 16, 2026 18:40
4637284 to
bab4e57
Compare
jeremybeard
marked this pull request as ready for review
October 16, 2026 19:11
wendtek
approved these changes
Oct 16, 2026
neel-astro
approved these changes
Oct 19, 2026
| fi | ||
|
|
||
| for file in $files; do | ||
| if [[ $file =~ ^"${{ inputs.root-folder }}".* ]]; then |
Collaborator
There was a problem hiding this comment.
curious q: do we need to normalize the root-folder, I mean stripping any "." or "/" at prefix ("./dbt"), I don't mind to skip it here if we are not doing it in dag/image deploy check?
Collaborator
Author
There was a problem hiding this comment.
It's done this way for all deploy types so will leave it like this.
jeremybeard
force-pushed
the
non-dag-bundles
branch
from
October 19, 2026 13:19
bab4e57 to
ba9d3b1
Compare
Co-Authored-By: Claude <[email protected]>
jeremybeard
force-pushed
the
non-dag-bundles
branch
from
October 19, 2026 14:34
ba9d3b1 to
3cd8fe5
Compare
This branch is waiting to be deployed
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.
Adds
deploy-type: non-dags(Astro CLI 1.44.0+), which deploys any directory as a non-DAG bundle mounted for DAGs to read. As withdbt, the directory isroot-folder. It is required, as ismount-path;non-dags-bundle-typeis an optional label.The bundle deploy step, shared with
dbt, also gains:bundle-trigger-paths, the bundle equivalent ofimage-trigger-pathsskip-unchangedsupportcreate-deployment-preview, never ondelete-deployment-previewValidation:
deploy-typeis now checked, where an unknown value used to deploy nothing.root-folderis required withnon-dags, since an empty one would deploy the whole repository.image-name,parse,pytestandbuild-secretsare rejected withnon-dags, as the CLI rejects them alongside--non-dags. Amount-pathon other deploy types is a warning.E2E, on one new bundle deployment: the non-DAG deploy, the skip and fallback paths, trigger-path parsing, a non-DAG deploy to a preview, and the delete guard.