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

Well, it's the multi-lang component that I wrote

Aha. It’d be looking for an executable in $PATH

```which pulumi-resource-aws
/Users/anton/.nix-profile/bin/pulumi-resource-aws```

So I’m guessing `which pulumi-resource-awslambdaapi` ?

These lines were supposed to take care of it:

```# Ensure the pulumi-provider-xyz script is on PATH
$ export PATH=$PATH:$PWD/bin```

<https://github.com/ajhool/pulumi-aws-apigateway-lambda>

There's what I'm working with. I did run that command -- I'll take a look at the path and see if anything looks odd

In bin I have `pulumi-resource-aws-lambda-api

So, that name might not line up with what my package name should be, when I was setting some of those names I was uncertain

Right that sounds like it can be a problem.

I’ve checked out you code, trying it out

Going to upvote this one: <https://github.com/pulumi/pulumi/issues/6929>

Where's the source of truth for the package name?

That’s the problem, it’s denormalized

Still working with your code, give me a sec. Trying to get the names consistent, if it works I’ll send a PR

Alright, I'm going through and removing aws-lambda-api and replacing it with "lambdaapi", which is the package name in typescript

Brute-force PR <https://github.com/ajhool/pulumi-aws-apigateway-lambda/pull/1>

I unfortunately went the other way (-&gt; “awslambdaapi”) but it gives you an idea of all the locations the name figures.

Files under sdk/ are auto-edited by Make but the rest are hand-edited