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

That question doesn’t parse to me, TBH. Do you have a rough example of what you’re trying to do?

const eventHandler = new aws.lambda.Function("event-handler", {
        handler: handlerName,
        runtime: aws.lambda.NodeJS8d10Runtime,
        role: handlerRole.arn,
        code: new pulumi.asset.AssetArchive({
            ".": new pulumi.asset.FileArchive(handlerPath),
        }),
    });

I'm creating a Function resource, and inside the code of that function I need it to be able to write to an SQS queue.

So I'm after the name of that queue to pass into the function somehow, but my understanding of the build process means that may be difficult...

In that case, best to pass the outputs in via `environment`. 

That’s also just good practice in general - deploying the same thing in dev and prod is a lot more achievable with twelve-factor configuration