Andre Brisco
Andre Brisco
@Tpt Sorry to ping on an old issue but just looking for clarification. With the release of `0.26.0`, I wasn't clear based on #5137 if function stubs were expected to...
Fantastic, thank you!
Maybe some history will help reveal a path forward: The original design of `helm_import_repository` was to support users specifying chart names, versions, and repositories, just as they would outside of...
Also, one thing that might be leading to some confusion is the `_repository` suffix is a pattern I've been using for all repository rules (I forget where I adopted that...
@Tpt seems like there was a conflict introduced in the merge queue for this one?
> What about maintaining two options? `helm_pull` to allow using `helm` and it's resolver logic to download a chart, which wouldn't be cacheable, and `helm_import_url` to download a specific chart...
> @abrisco, thoughts on [#197 (comment)](https://github.com/abrisco/rules_helm/pull/197#issuecomment-3254851548)? > > Looking at https://github.com/bazel-contrib/rules_jvm_external and https://github.com/bazel-contrib/rules_python, they use `coursier` and `pip` respectively, with optional support to write a file for downloading dependencies via...
Could you not add a `oci_push` target that re-uploads the external image and pass that to `images`?
What is the issue in referring to an image not tracked by Bazel? I don't think I understand the use case here.
What would prevent you from using the sha directly?