Alternative to Tiltfile for defining team-level config
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
We have a number of different Tiltfiles in use within our org, and are having some difficulty ensuring settings like experimental_telemetry_cmd, disable_snapshots and set_team are applied correctly everywhere.
It would be helpful to be able to decouple some of these settings from the "project" level settings. A few possible avenues:
- Environment variables, perhaps even defining an "always-run" Tiltfile
- A
.tiltrcfile - We have a monorepo, so something like Bazel's
WORKSPACEwould also be an option
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing how Tiltfiles are discovered and how experimental_telemetry_cmd, disable_snapshots, and set_team are loaded; compare the proposed environment-variable, .tiltrc, and workspace-level approaches. Done means one team-level configuration mechanism is selected and its behavior across multiple Tiltfiles is defined.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100