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

Storing it in a cloud vault is a viable option and makes it visible to tools and services that don't have access to the build or Pulumi CLI. But if your migration script is being called from somewhere with access to the Pulumi CLI, you can export the value from the Pulumi program, and call `pulumi stack output` to get those exported values

`export const connectionName = ...` is how you create a stack output.

`pulumi stack output connectionName --secret` will get you the value from the command line (if it contains secrets).

If it's a secret, storing in Secrets Manager is also a valid approach.

Usually it's a good sign when Paul and I agree. :wink:

Yep. Last time we didn't agree, there was a global financial crisis. That didn't go well.

I don't remember that per se, but I'll believe it. :wink:

Thanks <@U012UJTT55M> and <@U02FZC2RE0Y>! I will give it a try with using `pulumi stack output`