tilt-dev / tilt-dev/tilt

Provide metadata to the tilt dashboard that provides more information on what project you're working on.

Open
#4,533 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

I work in a micro-services architecture and often have multiple tilt dashboards up and running. One for each namespace in a K8s cluster. Example, inv for fetching inventory data, vendor for fetching vendor data, customer for fetching and managing customer data. I run tilt up for each of these repos and now have 3 very similar dashboards that are indistinguishable. I would love a way to provide some metadata to the dashboard that makes it easy to know which dashboard i'm looking at.

Current Behavior

Currently, there's not good way for me to identify which dashboard is which. They all look the same (See screenshots)

Why Do You Want This?

In my organization, this issue is felt by everyone. There is difficulty navigating which dashboard corresponds to which service when developing locally.

Additional context
Add any other context or screenshots about the feature request here.
image
image

Suggestions:

  • Provide a config to pass a title to the HTML <title> tag of the dashboard. This way you can name the browser tab, right now it just shows the status of the Tilt | n/N where n is the number of up and running resources and N is the total number of resources.
  • Provide a config or a param to the resource that can be displayed on the individual tiles?
  • Show info on the namespace a k8's resource is running or other meta data from the yaml file that tilt is running.

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

No files, tests, or entry points are named. Start by locating the dashboard HTML title and resource-tile rendering, then trace how Kubernetes namespace or other YAML metadata could reach them. Done means an agreed metadata or configuration path that clearly distinguishes multiple dashboards; the display location and supported metadata still need to be decided.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
devtools, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.