I suspect there may be an issue where Hasura would prefer UR

Question

I suspect there may be an issue where Hasura would prefer URL encoding and `db upgrade` prefer there would be an extra ` ` symbol

Zanie · Answer

Interesting Thanks for your report I ll look into a fix for that

Zanie · Answer

Hi < Aiden Price> looking at a fix for this and want to confirm the required behavior

Zanie · Answer

In the graphql deployment I d have ``` name PREFECT SERVER DATABASE CONNECTION URL value <postgresql prefect foobar prefect server postgresql default 5432 prefect>```

Zanie · Answer

While in the Hasura deployment I d have

Zanie · Answer

``` name HASURA GRAPHQL DATABASE URL value <postgresql prefect 40foobar prefect server postgresql default 5432 prefect>```

Zanie · Answer

Did you change this for just the db upgrade container and not the graphql container

Aiden Price · Answer

Hi Micahel sorry it took me a while to get back to you timezone differences In the `values yaml` I ve got `postgresql postgresqlUsername prefect 40foobar` so that I can still leverage all the helper functions But in graphql gt deployment in the `initContainers env` I changed `PREFECT SERVER DATABASE CONNECTION URL` to a hardcoded `<postgresql prefect> foobar foobar postgres database azure com 5432 prefect`

Aiden Price · Answer

I did not change the graphql gt deployment `containers env` at all so it still uses the `postgresUsername` from my values yaml

Aiden Price · Answer

No changes made to the Hasura deployment yaml at all so it should use values yaml as well

Zanie · Answer

Great thanks I ll open a pr with a fix today

Aiden Price · Answer

Thank you for that Love your work by the way

Zanie · Answer

Thank you Definitely leaned a lot on the community s contributions because it s my first helm chart but I m excited that it s working for people slightly smiling face

Zanie · Answer

If you get a chance please let me know if <https github com PrefectHQ server pull 139> fixes your issue I don t have an Azure cluster to test against right now

Aiden Price · Answer

Thanks Michael I dropped the database entirely and rebuilt it with the new `replace 40 ` line in the graphql deployment template Worked perfectly Thanks for your help with this

Zanie · Answer

Yay Let me know if there s anything else with the docs helm NOTES that needs clarification