I d like to use a Secret stored in Prefect Cloud in my run c

Question

I d like to use a Secret stored in Prefect Cloud in my run config I have stored the secret using ``` gt gt gt from prefect import Client gt gt gt client = Client gt gt gt client set secret name= test value= test gt gt gt client set secret name= AWS ACCOUNT ID dev value= 123456789098 ``` It seems like I should be able to use ```from prefect client import Secret aws account id = Secret AWS ACCOUNT ID + RUN ENV get ``` However I receive the following error ```ValueError Local Secret AWS ACCOUNT ID dev was not found ``` How can I retrieve a secret value outside of a task

Kevin Kho · Answer

If executing locally there is a config env variable and the default is to pull local secrets Set ```export PREFECT CLOUD USE LOCAL SECRETS=false``` and this will pull the Cloud Secret

Kevin Kho · Answer

This is set to false for agent cloud runs

Stephen Lloyd · Answer

Thanks Where should I have found tis parameter config setting

Kevin Kho · Answer

I guess it s not documented on the Secrets page but more generally configurable stuff can be found in the <https github com PrefectHQ prefect blob master src prefect config toml L55 L64|config toml>

Stephen Lloyd · Answer

Ah Should I have this config file stored locally Do the config selections get uploaded with a flow

Kevin Kho · Answer

You need them stored on where the flow is running or you can pass the env variables ```PREFECT CLOUD XXX XXX``` for example to your flow to them to take effect

Stephen Lloyd · Answer

Thanks so much

Stephen Lloyd · Answer

< Kevin Kho> Following up on this If I set via `export PREFECT SECRETS=false` I get the expected behavior If I change the default config path with `export PREFECT USER CONFIG PATH= Users slloyd projects my path prefect` with `use local secret=false` I do not get the expected behavior If I put the file in `$HOME prefect config toml` with `use local secret=false` in a docker image I do not get the expected behavior Do you know what I am missing

Kevin Kho · Answer

I have noticed the same thing too with the `config toml` in Docker Would you be willing to write an issue about it I can also open one and you can add your details there You can use the RunConfig as that works