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

If I want to generate a Cloudwatch Dashboard that aggregates all lambda function, should the approach I take be to use the AWS SDK to collect the function names?  I’m not sure I should be updated 20+ projects to start exporting the Lambda Ids to be used as stackoutputs. Or does Pulumi have  another way to collect ids of resources Pulumi manages?

Right now StackReference only exposes the outputs, not all the resources. So if you wanted to get these from other stacks that way - you’d need to make the function names stack exports. 

It may well make sense to expand StackReference to get details of resources other than the stack outputs.

If you have some way to identify which functions you want, using the AWS SDK directly is certainly an option. 

Yeah, I would use the tags I’ve autotagged my resources with