tilt-dev / tilt-dev/tilt

Provide a way to list the available project resources without starting up everything to help product owners discover them

Open
#5,374 5 comments 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

Describe the Feature You Want

I would love to see a command like:

> tilt list
backend
frontend
storybook
database
db-ui
frontend-test

# or
> tilt list-resources
backend
frontend
storybook
database
db-ui
frontend-test

That allows a user to discover the available resources without having to run tilt up and already consuming the necessary CPU, RAM, ... just to see the available service names that could be started separately.

Current Behavior

Currently, we recommend our product managers to:

  • use tilt up and read the names in the web ui
  • scroll through the Tiltfile and use everything that has name="..."
Why Do You Want This?

We've recently introduced Tilt to help new developers onboard quicker and unify development environmentes. We've also introduced it to allows product owners to test PRs more quickly.

The proposal would be especially helpful for our product owners/project managers that lack the technical skill to read the Tiltfile and sometimes work on resource constrained machines. It would also help our developers (although to a lesser extend, as they are able to read Tiltfiles more easily).

Additional context

I've searched through the github issues and the documentation but was not able to find this feature. It surprised me that this does not exist, so I'm thinking that it is rather me who missed something than the feature actually not being available.

Thanks for building Tilt - we soon want to introduce it everywhere as initial feedback from both devs and PMs has been great!

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 proposed tilt list or tilt list-resources CLI entry point and compare it with the current tilt up workflow described in the issue. Done means the command lists resources such as backend and frontend without starting services or consuming runtime resources.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.