Allow complex depency flow by adding resource_deps to more functions
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
I have multiple services set up with multiple tilt files. For testing I sometimes run tilt files one by one, but to setup the whole cluster I want to be able to run all of them through a single Tiltfile, while still respecting decency flow.
The resources and resource_deps are perfect for this, however, they are only present on functions that create resources themselves (k8s, local, dc etc.), while for my use case I imagine I would need a resource_deps on the load_dynamic function.
Is there another way to go about dynamic and staged loading with multi Tiltfiles while still allowing them to be executed separately?
If not, I would like to propose adding resource_deps to other functions, such as load_dynamic
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the Tiltfile loading entry point and the existing resource_deps handling on k8s, local, and dc functions, then trace load_dynamic's behavior. Define whether load_dynamic should accept resource_deps or another supported mechanism while preserving standalone and aggregate multi-Tiltfile execution, and validate the chosen behavior with relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100