I suspect there may be an issue where Hasura would prefer UR Prefect Community #prefect-server

I suspect there may be an issue where Hasura would...

Aiden Price

11/17/2020, 9:34 AM

I suspect there may be an issue where Hasura would prefer URL encoding and

db-upgrade

prefer there would be an extra

symbol.

Zanie

11/17/2020, 1:33 PM

Interesting! Thanks for your report, I’ll look into a fix for that.

Zanie

11/17/2020, 7:34 PM

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

Zanie

11/17/2020, 7:34 PM

In the graphql deployment I’d have

Copy code

- name: PREFECT_SERVER__DATABASE__CONNECTION_URL
value: <postgresql://prefect@foobar@prefect-server-postgresql.default:5432/prefect>

Zanie

11/17/2020, 7:34 PM

While in the Hasura deployment I’d have

Zanie

11/17/2020, 7:35 PM

Copy code

- name: HASURA_GRAPHQL_DATABASE_URL
value: <postgresql://prefect%40foobar@prefect-server-postgresql.default:5432/prefect>

Zanie

11/17/2020, 7:40 PM

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

Aiden Price

11/17/2020, 10:31 PM

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 > 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

11/17/2020, 10:32 PM

I did not change the graphql > deployment

containers.env

at all so it still uses the

postgresUsername

from my values.yaml

Aiden Price

11/17/2020, 10:33 PM

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

Zanie

11/17/2020, 11:39 PM

Great thanks! I’ll open a pr with a fix today.

Aiden Price

11/17/2020, 11:39 PM

Thank you for that. Love your work by the way!

Zanie

11/17/2020, 11:42 PM

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 🙂

Zanie

11/18/2020, 12:06 AM

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

11/18/2020, 3:28 AM

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

11/18/2020, 4:01 AM

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

2 Views

Open in Slack

Previous Next