Hi all, I'm just starting with Prefect this weeken...
# ask-community
j
Hi all, I'm just starting with Prefect this weekend, and I can't seem to find the answer to a perhaps simple question: it looks like once I ran
prefect server start
once, I can no longer get the ephemeral server to come up when I test the flow. Upon some debugging, it looks like the presence of ~/.prefect/profiles.toml is causing that problem. Actively set the profile to "ephemeral" doesn't help. What is the right way of getting back to the initial state? Just delete the profiles.toml?
n
hi @Joe if you do a
prefect config view
you'll see which
PREFECT_API_URL
is currently being used and where its being set
j
If I start from scratch, I can run the flow with the ephemeral server.
prefect config view
shows:
Copy code
pipeline git:(pipeline_pg) ✗ prefect config view                                      <aws:my-sso>
PREFECT_PROFILE='ephemeral'
PREFECT_SERVER_ALLOW_EPHEMERAL_MODE='true' (from profile)
👍 1
looks like
PREFECT_API_URL
is not set. But when I do
touch ~/.prefect/profiles.toml
, I can no longer run it with the ephemeral server. I get
ValueError: No Prefect API URL provided. Please set PREFECT_API_URL to the address of a running Prefect server.
So in both cases
PREFECT_API_URL
is not set. But the presence of an empty
profiles.toml
changed the behavior.
n
hrm that sounds like a bug. can you open an issue for that?
j
What's the link to file a bug?
j
Will do
n
thanks! in the interim you've gotten it to work by setting the
PREFECT_API_URL
?
j
Only if I run a Prefect server. But for local development, that's cumbersome, so I just keep deleting
~/.prefect/profiles.toml
.