Check if a dependency is installed
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Oftentimes a Tiltfile can itself require other tools to be installed: like helm (though we handle that case internally), or jq if you're doing some complex JSON manipulation. It would be nice if Tilt:
a) Provided a way to detect if something is in the $PATH (this could maybe be an extension) and fail if it isn't
b) Provided a way to install something if it find that it doesn't exist.
c) stretch goal: deal with versioning/pinning versions
All of these things can be done in one-off ways with local(_resource)s but we should have a recommended/supported pattern for doing it
This was inspired by a convo with zetaron in k8s slack
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
Start with the Tiltfile dependency examples using local(_resource), including the existing internal handling for helm. Done should mean a supported pattern can detect missing PATH tools and fail clearly, with installation and version pinning addressed if the scope is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100