broad-boots-45639
01/21/2020, 6:21 PM--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?gorgeous-egg-16927
01/21/2020, 6:29 PMbroad-boots-45639
01/21/2020, 6:33 PMconst 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" }
})
gorgeous-egg-16927
01/21/2020, 6:35 PMsumologic.endpoint
, you would need
sumologic: {
endpoint: "<URL>"
}
broad-boots-45639
01/21/2020, 6:37 PM