Support executable wrappers in `uv_toolchain`
Nobody has claimed this yet.
Assessment
This issue has not been assessed yet.
Description
🚀 feature request
Relevant Rules
uv_toolchain and lock.
Description
I want to use a custom uv wrapper with the lock rule. In my case, the wrapper would obtain credentials and set index authentication variables before calling the pinned uv binary.
There are a couple of issues right now. First, uv_toolchain rejects executable targets with multiple output files. Second, lock forwards the executable without preserving its runfiles, which limits wrappers that depend on runtime files or symlinks.
Describe the solution you'd like
Allow uv_toolchain to accept executable wrappers with multiple output files. Preserve their runfiles, including ordinary symlinks and root symlinks, in both lock build actions and .run targets.
Export the downloaded uv binary with public visibility so wrappers can declare it as a runtime dependency.
I'll open a PR for this in a bit.
Describe alternatives you've considered
Patching rules_python.
- Dominant language
- Starlark
- Stars
- 690
- Forks
- 722
- Avg merge
- 1d 55m
- Merged PRs (30d)
- 38
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.
More from bazel-contrib/rules_python
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bazel-contrib/rules_python#4164 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bazel-contrib/rules_python#3821 ·
-
bazel-contrib/rules_python#4179 ·
-
Release 2.4.0 Opentype: release
Difficulty 4/5 3-5 days Newbie friendliness 25/100
bazel-contrib/rules_python#4175 · 3 comments ·
-
Release 2.3.4 Opentype: release
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
bazel-contrib/rules_python#4173 · 2 comments ·