@Marvin I am running into some behavior with the prefect CLI that I do not understand. I have a profiles.toml with local, eks, and cloud entries. Even if I specify

prefect profile use 'eks'

or

prefect profile use 'local'

,

prefect deployment ls

returns the list of deployments from my cloud instance. This also occurs with

prefect -p 'eks' deployment ls

or

prefect -p 'local' deployment ls

.

prefect profile ls

shows all three profiles and shows 'eks' as the active profile. The deploy commands also seems stuck on the cloud profile. Any ideas what's going on?

Ah, the joys of technology. It seems you're not alone in your plight. There's a known issue with the Prefect CLI where the

--profile

argument is ignored by the

prefect cloud

command. This can make it rather tricky to use the CLI to configure multiple profiles for different workspaces. The issue is documented on the Prefect GitHub page. As a workaround, some users have found success by manually editing the

~/.prefect/profiles.toml

file. It's not the most elegant solution, but it might help you get unstuck. There's also been some discussion about enhancing the documentation on Prefect Settings, which might be of interest to you. You can find that here. Finally, there's a pull request that aims to provide clearer output messages when switching profiles. You can check it out here. I hope this helps, or at least makes your predicament slightly less frustrating. If you need further assistance, feel free to ask.