tilt-dev / tilt-dev/tilt

Ability to pause tilt reload on demand

Open
#2,959 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
10.1k
Forks
413
Avg merge
1d 10h
Merged PRs (30d)
6

Description

Occasionally, I need to stop work on an in-development branch to make a small amount of changes on a new branch. These changes don't necessarily need to run through tilt. At the same time, I'd like to quickly be able to switch back to what I was doing with minimal interruptions. Switching branches can have a number of bad side effects while tilt is running. E.g.

  • I may have feature flags/tilt config that is incompatible with a new base branch
  • The cluster may be in a specific hard to reproduce state

It would be nice to be able to temporarily pause resource reload (either from the terminal or GUI), change branches and make changes, then switch back to the original branch. and resume resource reloading.

A possible workaround today would be to instrument either a tilt_config option or environment variable and stop tilt prior to switching branches. A rough (untested) example is below.

tilt up
# in another terminal
tilt arg -- --preserve-resources all

# Tiltfile
if cfg.get('preserve-resources', []) != 'all':
   # Usual Tiltfile config
else:
   # No resources are defined, so tilt shouldn't try and delete anything
   pass

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the proposed tilt arg -- --preserve-resources all workaround and the requested terminal or GUI control. Define how pausing should preserve the current cluster state while branches change, and how resuming should restore resource reloading without unwanted interruptions.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.