Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hi folks. I’m trying to upgrade the Helm chart, to get it to re-create the default tenant for me. It tells me `'postgresqlPassword' must not be empty` even though I am passing it with `--set` on the `helm upgrade` command-line.

```% CHART_NS=prefect
CHART_NAME=prefect-server-initial
helm upgrade \
--set ui.apolloApiUrl=http://${CHART_NAME}-apollo:4200/graphql \
--set agent.enabled=true \
--set jobs.createTenant.enabled=true \
--set postgresqlPassword=$POSTGRESQL_PASSWORD \
${CHART_NAME} \
prefecthq/prefect-server
Error: UPGRADE FAILED: template: prefect-server/charts/postgresql/templates/NOTES.txt:59:4: executing "prefect-server/charts/postgresql/templates/NOTES.txt" at &lt;include "common.errors.upgrade.passwords.empty" (dict "validationErrors" (list $passwordValidationErrors) "context" $)&gt;: error calling include: template: prefect-server/charts/postgresql/charts/common/templates/_errors.tpl:18:48: executing "common.errors.upgrade.passwords.empty" at &lt;fail&gt;: error calling fail: HELM_ERR_START
PASSWORDS ERROR: you must provide your current passwords when upgrade the release
    'postgresqlPassword' must not be empty, please add '--set postgresqlPassword=$POSTGRESQL_PASSWORD' to the command. To get the current value:

        export POSTGRESQL_PASSWORD=$(kubectl get secret --namespace prefect prefect-server-initial-postgresql -o jsonpath="{.data.postgresql-password}" | base64 --decode)
HELM_ERR_END```

Hi <@U02BCPNCV61> - this is after you added the password as an environment variable, right?

(I checked the env var afterward to make sure it got a reasonable-looking value)

Hm I think to set the password you might need to pass `postgresql.postgresqlPassword` instead of just `postgresqlPassword`

Just to follow up - were you able to get the upgrade working?

I ended up nuking the install and doing it afresh before you pointed out the correct spelling. But, after looking at `values.yaml`, I am convinced it would work when spelled with the `postgresql.` prefix