Hey guys, I’m upgrading from 0.12.2 to 0.13.12 and having some problems. Previously I was able to set env variables to override the graphql endpoint, and a bunch of other things, but it doesn’t seem to accept the format I had anymore. Previous variable:

PREFECT__SERVER__UI__GRAPHQL_URL

Not working with 0.13.12 Docs seem to suggest that it’s changed

graphql_url

to

apollo_url

, so I tried to update the env var to

PREFECT__SERVER__UI__APOLLO_URL

or even

PREFECT__SERVER__SERVER__UI__APOLLO_URL

but no luck. Any suggestions? Also tried

PREFECT__TELEMETRY__SERVER__TELEMETRY__ENABLED=false

to disable telemetry but no luck there either

Hi @Darragh - have you tried setting these variables in

~/.prefect/config.toml

?

Hey @nicholas no I haven't, as the deployment setup I'm using us fully automated, including the variable overrides. So right now I deploy prefect to an ec2 instance, and set a bunch of env vars from our CI/CD pipeline, and then start prefect. If I was to go the toml route is have to install prefect and then add a bunch of scripts to search and replace the variables in place in the toml. Not the end of the world to change to that, but I'd prefer to stick to the current method if it'll still work..

Hm ok - well to start, I think your telemetry variable should be:

PREFECT__SERVER__TELEMETRY__ENABLED=false

Yeah i tried the apollo one, no joy... Is there one for debug logging or something that I can turn on, just to test if it's picking any up at all?

I don't think there's a debug log for that but you could try execing into the UI container or visiting

<http://your_machine_endpoint:8080/settings.json>

, which should show you what setting the UI is inheriting

Good call, had no idea that was there 😄 settings.json only has this in it:

{
  "server_url": "http://$CORRECT_IP:4200/graphql"
}

No mention of the apollo_url

nope that's perfect, so that IP address is correct?

Yeah the IP is correct, but in the UI it keeps failing the graphql connection check until I set it manually. Set it manually and then it connects

Can you try resetting that variable? (there's a reset button in the input where you set the connection manually)

Button doesn’t seem to do anything… 🤔

Can you screenshot what you see there?

When you reset, that input isn't cleared and your configuration doesn't show up?

Sorry for the delay, think I misunderstood you yesterday. I did a clean deploy today, with the env vars, etc.. and the UI couldn’t connect to graphql, and the initial data in that input field was a greyed out “http://loclahot:4200/graphql”, but when I hit the reset it did display the correct IP which confused me greatly 🙂

No worries, that's usually a result of caching of the old value on a non-clean deploy. It sounds like you got it working now though?

Nope, that was a clean deploy I just did and still had to do the manual reset to get it picking up the right endpoint…

Right, the cache is browser-side

Hmm, not sure I follow…. So if I do a clean deploy, env var set etc… and then open the UI for the first time, why would it not have the correct value set?

Since the Prefect UI is a purely front-end application, the cache is set in your browser based on its knowledge of the prefect application; if your browser has an old value in the cache from a previous visit to the Prefect UI (even if it's a different installation), you need to clear it, which is what the reset button is doing.

Hmm, interesting. I was pretty sure I had done that, but I’ll test again in an incognito window and confirm!

@Darragh - so on a clean install you're not seeing the correct apollo endpoint at

<http://your_server:8080/settings.json>

?

In the json yes, but not in the ui