tilt-dev / tilt-dev/tilt

Support Tiltfile args with `tilt enable`

Open
#6,341 1 comment 0 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

Describe the Feature You Want

Similar to how you can define a group of services to use with tilt up and tilt down, I'd like to be able to do the same with tilt enable

Current Behavior

After configuring as per the link above, tilt enable group_name gives an error about "no such resource"

Why Do You Want This?

Suppose I have two groups, server and subset.

I can use tilt up to run everything, tilt up server to only run backend stuff, and tilt up subset to run a subset of frontend related services.

However, if I start via tilt up server and then change my mind, I have to either run tilt enable frontend_a frontend_b frontend_c or run tilt down followed by tilt up. Similarly, if I use tilt up server followed by tilt down subset, I end up in the same place.

I imagine this might be possible in a tedious fashion via local_resource duplicates of the same groups, but that seems undesirable.

Additional context
N/A

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

Start with the tilt enable command and the Tiltfile service-group behavior described in the linked documentation. Trace why a group name is reported as “no such resource”; done means tilt enable group_name accepts the defined group and enables its services consistently with the described tilt up and tilt down behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.