No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Your `Pulumi.dev.yaml` file will be automatically read when `dev` is your active stack. The calls you see in the code are configuration settings which will be overlayed on top of what is in the file. This gives you the option to have some values committed to source control and to add (or overwrite) some values which come from somewhere else.

<@UK4HNFLCB> I am using the inline way of automation API and upon printing context, I see that the config is nil - `Config:map[string]string(nil)` . That makes me believe `<http://Pulumi.dev|Pulumi.dev>.yaml` is not being read as a part of the context. Is the behavior you are talking about different from normal Pulumi programs than automation API programs?

We have an external configuration file &amp; describes how we want to our pulumi code to construct the instructions &amp; we fetch the name via EnvVar &amp; then read the file in using viper (or similar).  We do this in the main function before we call pulumi.Run()
``````