acoustic-carpenter-78188
02/25/2026, 11:41 PM.flyteinclude as an allowlist alternative to .flyteignore for code bundle control
• When present in root_dir, only the listed paths are bundled — no ignore filtering applied
• When absent, all existing behaviour is completely unchanged
Motivation
In large monorepos, .flyteignore requires enumerating hundreds of directories to exclude.
.flyteinclude flips this: list only what you need, everything else is excluded automatically.
# .flyteinclude
lib1/
lib2/
root-dir and .flyteinclude
.flyteinclude must live at root_dir and all patterns are resolved relative to it. For monorepos, point root_dir at the repo root:
flyte run --root-dir /path/to/monorepo workflow.py my_task
Test plan
- `pytest tests/flyte/code_bundle/test_include.py -v`
- `FlyteInclude` unit tests: no file, valid patterns, empty file
- Integration: `.flyteinclude` present → only listed dirs in bundle + tarball
- Integration: `.flyteinclude` absent → normal walk unchanged
flyteorg/flyte-sdkacoustic-carpenter-78188
02/27/2026, 5:58 AM