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

I haven’t used pulumi with golang but I guess I can still be helpful :wink:

do you want to use that from another pulumi stack?

If it’s within the same stack, you don’t have to even export it. You should be able to simple reference the variable internally in golang code.

(see <https://github.com/pulumi/examples/blob/master/aws-go-s3-folder/main.go> where BucketPolicy references previously created Bucket, saved in `siteBucket` variable)

If you want to reference that in a separate Pulumi stack, you want to use StackReference.

<https://www.pulumi.com/docs/tutorials/aws/aws-ts-stackreference/>

in that case, the stack you want to import something from MUST declare the variable as the output (using `ctx.Export`)

So I need to write pulumi code in Imperative style,

also one more question, is pulumi.Run only called once in a given stack?

I don’t think you should write it in imperative style… the whole pulumi concept is being declarative. I hope you didn’t misunderstand me somehow.

Regarding your last question, cannot say for sure (no pulumi golang experience) but I guess you shouldn’t have more than one `pulumi.Run` invocation.

Each program (regardless of the programming language used) basically declares the resources and then pulumi engine (not sure if that’s the name used by Pulumi team) based on that performs a reconciliation loop by trying to match the actual state with the one written (declared) by you.

Not sure how much experience you have with similar tools (like terraform) so if you have any more questions, feel free to ask them :slightly_smiling_face: