Resource trigger mode UI overrides get reset on Tiltfile reload
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Expected Behavior
- Tilt remembers overrides from UI throughout a session, even if Tiltfile is re-evaluated
Current Behavior
- Tiltfile evaluation resets trigger modes to values as defined there, losing any UI overrides
Steps to Reproduce
tilt upon a project- Change a trigger mode in the UI
touch Tiltfile
About Your Use Case
Many workflows can trigger a re-evaluation of the Tiltfile, so it's frustrating to have these reset seemingly at random during development.
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
Reproduce the issue by running tilt up, changing a resource trigger mode in the UI, and touching the Tiltfile. Trace how trigger modes are stored during Tiltfile re-evaluation; done means UI overrides remain unchanged after reload, while values defined in the Tiltfile still apply when no UI override exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100