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

• <https://www.pulumi.com/registry/packages/aws/api-docs/apigatewayv2/api/>
```_, err := apigatewayv2.NewApi(ctx, "example", &amp;apigatewayv2.ApiArgs{```
should be
```_, err = apigatewayv2.NewApi(ctx, "example", &amp;apigatewayv2.ApiArgs{```
without the colon before the equals sign because the first variable is not defined
• <https://www.pulumi.com/registry/packages/aws/api-docs/apigatewayv2/route/>
```_, err = apigatewayv2.NewRoute(ctx, "exampleRoute", &amp;apigatewayv2.RouteArgs{```
here it seems correct

This type of error, where `_` is used as a placeholder (?) and the definition uses `:=` seems to be very common.

This may just be a Golang thing (I don’t know enough about your code). But if you create a couple of resources where you are “throwing away” one of the values (like `_, err := blah` and then later `_, err := otherblah`, it will flag the second one as incorrect (because you aren’t defining any new variables. That’s why you have to use `_, err = otherblah`. I probably didn’t do a great job of explaining this, but hopefully it helps a little!

`_, err = ...` is a compile error if the `err` variable hasn't been declared elsewhere. `_ err := ...` is a compile error if the `err` variable is declared elsewhere. So our code generator has to change which one it uses based on if any other uses of `err` have happened before.