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

Hi there I was curious if this was a piece of documentation I was missing but I went down a rabbit hole around how `context.Context` eventually gets passed into pulumi from the automation auto package -&gt; my pulumi program, I was expecting it to just seamlessly pass down the context object but then I discovered it runs GRPC as a background process to run the various infra parts. Is this documented somewhere that your context doesnt get passed when using the automation api in go?

:wave:  I don't know if there's anything that specifically answers your question

you've read through:
<https://www.pulumi.com/docs/iac/concepts/how-pulumi-works/>
<https://www.pulumi.com/docs/iac/automation-api/concepts-terminology/>
<https://pulumi-developer-docs.readthedocs.io/latest/docs/README.html>

but still have a question around _how_ `context.Context` is passed around or _what_ the content of `context.Context` is populated with when executing against an Automation API workspace?

There is nothing really there about golang specific features that I can quickly see. I was just expecting the context I populated to give to the `Up` would be passed to the `pulumi.Context.Context` but it deosnt look like that happens cause it run through grpc? So its just not possible to share it? Or is this a oversight?