Describe the Feature You Want
Native support for service grouping/stacking and auto-discovery from filesystem scanning.
Ideally:
- Services could be tagged with a
group or stack label in their Tiltfile/resource definition
tilt up --group=frontend would start all resources with that label
- Tilt could optionally auto-discover resources by scanning for
Tiltfile or config files in subdirectories
Current Behavior
Currently, to start a subset of related services, users must either:
- List all service names manually:
tilt up service-a service-b service-c ...
- Maintain shell scripts or wrappers that track which services belong to which groups
- Use
include() in the main Tiltfile but still manually register each subdirectory
There doesn't appear to be a native way to:
- Tag resources with logical groupings
- Auto-discover resources from filesystem structure
- Filter
tilt up by group/tag
Why Do You Want This?
Working with a monorepo containing ~40 microservices organized by domain. Common workflows:
- Start just the "frontend" services (5-8 resources)
- Start just the "backend-api" services (10-12 resources)
- Start a specific feature stack that spans multiple domains
Currently building a thin wrapper tool that:
- Scans for manifest files in the monorepo
- Extracts a custom
stack field
- Calls
tilt up with the filtered service list
Would prefer to use native Tilt patterns if they exist or are planned.
Additional context
Add any other context or screenshots about the feature request here.
- Monorepo structure:
/services/<domain>/<service-name>/Tiltfile
- Each service already has metadata files (similar to docker-compose.yml or manifest)
- Currently using
include() in main Tiltfile but requires manual registration of each service
- Looked into
local_resource for discovery but feels like a workaround
Describe the Feature You Want
Native support for service grouping/stacking and auto-discovery from filesystem scanning.
Ideally:
grouporstacklabel in their Tiltfile/resource definitiontilt up --group=frontendwould start all resources with that labelTiltfileor config files in subdirectoriesCurrent Behavior
Currently, to start a subset of related services, users must either:
tilt up service-a service-b service-c ...include()in the main Tiltfile but still manually register each subdirectoryThere doesn't appear to be a native way to:
tilt upby group/tagWhy Do You Want This?
Working with a monorepo containing ~40 microservices organized by domain. Common workflows:
Currently building a thin wrapper tool that:
stackfieldtilt upwith the filtered service listWould prefer to use native Tilt patterns if they exist or are planned.
Additional context
Add any other context or screenshots about the feature request here.
/services/<domain>/<service-name>/Tiltfileinclude()in main Tiltfile but requires manual registration of each servicelocal_resourcefor discovery but feels like a workaround