Uh oh!
There was an error while loading. Please reload this page.
Add --exclude-from and --include-from flags to sync command - #2660
Merged
Conversation
anton-107
marked this pull request as ready for review
April 4, 2025 15:33
anton-107
requested review from
andrewnester, denik, pietern and shreyas-goenka
as code ownersApril 4, 2025 15:33
denik
reviewed
Apr 7, 2025
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
denik
reviewed
Apr 7, 2025
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
pietern
reviewed
Apr 14, 2025
pietern
left a comment
Contributor
There was a problem hiding this comment.
I expect --include-from to be almost identical, could you include it in this PR?
Separately, I would prefer if we not use .databricksignore even in our test files. It implies (to me) there are semantics associated with this file name, even though that's something we explicitly don't want.
anton-107force-pushed
the
anton-107/sync-excludefrom
branch
from
April 17, 2025 13:27
6ba54a9 to
76acd9bCompareanton-107temporarily deployed
to
test-trigger-is
April 17, 2025 13:28 — with 
GitHub Actions
Inactive
anton-107temporarily deployed
to
test-trigger-is
April 17, 2025 13:49 — with GitHub Actions
Inactive
anton-107temporarily deployed
to
test-trigger-is
April 17, 2025 13:56 — with GitHub Actions
Inactive
anton-107temporarily deployed
to
test-trigger-is
April 17, 2025 14:08 — with GitHub Actions
Inactive
…isting / missing) 2) refers to exact directory (existing / missing) 3) contains "**"
anton-107temporarily deployed
to
test-trigger-is
April 17, 2025 14:22 — with GitHub Actions
Inactive
anton-107temporarily deployed
to
test-trigger-is
April 17, 2025 14:44 — with GitHub Actions
Inactive
denik
reviewed
Apr 17, 2025
Uh oh!
There was an error while loading. Please reload this page.
andrewnester
approved these changes
Apr 22, 2025
Uh oh!
There was an error while loading. Please reload this page.
deco-sdk-taggingBot
added a commit
that referenced
this pull request
Apr 23, 2025
## Release v0.249.0 ### CLI * Added `exclude-from` and `include-from` flags support to sync command ([#2660](#2660)) ### Bundles * Correctly translate paths to local requirements.txt file in environment dependencies ([#2736](#2736)) * Check for running resources with --fail-on-active-runs before any mutative operation during deploy ([#2743](#2743))
denik pushed a commit
that referenced
this pull request
May 20, 2026
## Why <!-- Why are these changes needed? Provide the context that the reviewer might be missing. For example, were there any decisions behind the change that are not reflected in the code itself? --> Exclude-from flag allows users to exclude file patterns from sync operations by providing a .gitignore -like file containing file patterns that should be excluded from sync Usage: `$ databricks sync <SRC> <DEST> --exclude-from .my-exclude-file` `$ databricks sync <SRC> <DEST> --include-from .my-include-file` ## Tests <!-- How have you tested the changes? --> 1. Added new acceptance tests 2. Added new unit test <!-- If your PR needs to be included in the release notes for next release, add a separate entry in NEXT_CHANGELOG.md as part of your PR. -->
denik pushed a commit
that referenced
this pull request
May 20, 2026
## Release v0.249.0 ### CLI * Added `exclude-from` and `include-from` flags support to sync command ([#2660](#2660)) ### Bundles * Correctly translate paths to local requirements.txt file in environment dependencies ([#2736](#2736)) * Check for running resources with --fail-on-active-runs before any mutative operation during deploy ([#2743](#2743))
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Why
Exclude-from flag allows users to exclude file patterns from sync operations by providing a .gitignore -like file containing file patterns that should be excluded from sync
Usage:
$ databricks sync <SRC> <DEST> --exclude-from .my-exclude-file$ databricks sync <SRC> <DEST> --include-from .my-include-fileTests