This message was deleted.

I'm not intimately familiar with API Gateway, but from a quick look I don't see any reason why you couldn't do this.

@gentle-diamond-70147 is that something you see possible by looking at Pulumi docs? what gives you that indication?

Not specifically for API Gateway. In general, any resource ID can be an output from a stack and then you can use that via stackreference as an input for resources in another stack. So, my quick look at https://www.pulumi.com/docs/reference/pkg/aws/apigatewayv2/route/#basic confirmed you could pass the API Gateway ID into a Route - e.g. https://www.pulumi.com/docs/reference/pkg/aws/apigatewayv2/route/#basic.

@early-glass-64522 Maybe this is what you're looking for? Inter dependencies? https://www.pulumi.com/docs/intro/concepts/organizing-stacks-projects/#inter-stack-dependencies This is what I am going try out tonight to see how to run a lambda function from one repo, and reference an SQS queue that was created in another repo. Both repos are different projects, at least that's the way I see it happening

@gentle-diamond-70147 oh yeah! that’s what I was looking for! Thanks