Having trouble passing in values to a Helm chart via Pulumi. The chart is failing to install because an access id I am passing in as a value isn’t valid. I know it is valid because I can install the helm chart manually, passing in the secret with

--set

. Pulumi looks to be writing these values into a yaml file in tmp, but they’re cleaned up as soon as the command fails: Command failed: helm template /tmp/tmp-2518liO6nRLE4N1X/sumologic --name-template sumobundle --values /tmp/tmp-2518liO6nRLE4N1X/sumologic/values.yaml --values /tmp/tmp-25188Uk68Vj0j9UB.yaml --namespace sumologic I’d like to validate the values in these files and confirm that the secrets are being passed in. Before I do something hacky, is there a better way I could go about troubleshooting this problem or maybe force Pulumi to retain its artifacts from the preview?

We don’t currently expose a way to keep those files around after failure. I can take a look if you want to post the code snippet you’re using for the Chart + values

Thanks!

const helm = new kubernetes.helm.v2.Chart("sumobundle", {
    fetchOpts: {
        repo: "<https://sumologic.github.io/sumologic-kubernetes-collection>"
    },
    chart: "sumologic",
    namespace: "sumologic",
    values:
        {
            "sumologic.endpoint": "<https://api.us2.sumologic.com/api/v1/>",
            "sumologic.accessId": "secret",
            "sumologic.accessKey": "alsosecret",
            "prometheus-operator.prometheus.prometheusSpec.externalLabels.cluster": "mycluster",
            "sumologic.clusterName": "mycluster"        }

})

Ah, the problem is with the keys in your values dict. Instead of

sumologic.endpoint

, you would need

sumologic: {
  endpoint: "<URL>"
}

Thanks for the tip! I'll do so.