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

Depends whether you check it into source control or not. Do you mean, do the values get pushed to the state?

It’s not in source control in this instance as it’s dynamically generated in a CI pipeline

I can generate it and make it available in later steps, but it was just a bit surprising to me

I did some config on my machine, then in the pipeline and realised the two didn’t converge

I just assumed it was pushed as part of the stack

Which is probably an oversight on my behalf

I guess just using git in most scenarios provides the most obvious solutions since its’ encrypted anyway

it gets generated when you do something that involves config. That might be that you've set a non-default secret provider, or setting a config from somewhere else

I’m setting config values in my CI pipeline

For the time being I guess I can just let it exist for the lifetime of the pipeline and if I need traceability I can manually push/pull to GCS

just assumed it was part of the whole ‘tracked state’ package