Add option to pass values.yaml to helm_upgrade

[borg286]

I'd like to be able to have a bazel rule that generates a values.yaml file and pass that into a helm_upgrade target.
Currently I'd have to hard-code them in the opts array, and it looks fairly ugly.
Currently the only way to pass in values is with helm_chart or helm_package, but if I import the helm chart via helm_import_repository, then I don't have a way to pass in values.yaml.

[johansja]

Not sure if the issue I'm currently facing is identical to this. Basically I defined a BUILD file and a few values.yaml which looks like this:

load("@rules_helm//helm:defs.bzl", "chart_file", "helm_chart")

chart_file(
    name = "file",
    api_version = "v2",
    app_version = "{BUILD_EMBED_LABEL}",
    chart_name = "sample",
    description = "A Helm chart for Kubernetes",
    type = "application",
    version = "0.1.14",
)

helm_chart(
    name = "test",
    chart = ":file",
    images = ["//src/docker/sample:push"],
    install_name = "sample",
    values = "values.yaml",
)

helm_chart(
    name = "staging",
    chart = ":file",
    images = ["//src/docker/sample:push"],
    install_name = "sample",
    values = "values-staging.yaml",
)

helm_chart(
    name = "production",
    chart = ":file",
    images = ["//src/docker/sample:push"],
    install_name = "sample",
    values = "values-production.yaml",
)

Upon issuing bazel run --stamp --embed_label 2024032201 //:test.upgrade, I noticed that whatever changes that I have done in values.yaml won't be reflected in the release.