tilt-dev / tilt-dev/tilt

determine how long it took between when a resource started running and when it became ready

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

Currently, Tilt publishes APIs to help you determine how long a local server has been running:
https://api.tilt.dev/core/cmd-v1alpha1.html

There's also an API to determine the current readiness state:
https://api.tilt.dev/interface/ui-resource-v1alpha1.html

But there's currently no API to help you figure out how long the resource took to become ready.

Additional context

This overlaps with a bunch of other things we're working on right now, including:

I think the right short-term way to do this would be to add a few metav1.Condition objects to UIResource:
https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Condition

In particular, we could have a "Ready" condition (for when a UIResource becomes ready) and a "Started" condition (for when a resource is first deployed / first starts 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

Start by reading the UIResource API documentation and the metav1.Condition definition referenced in the issue, then inspect how current resource readiness and running state are exposed. Done means the API exposes Started and Ready conditions for a UIResource so callers can determine the time between deployment or startup and readiness, with the interaction with waiting and resource dependencies understood.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
api, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.