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

the API gateway is part of a Pulumi component resources, so you don't have direct access to the resource properties. You can do it via a transformation: <https://www.pulumi.com/docs/intro/concepts/resources/#transformations>

Is there a reason you want to do this? it could create outages

Yeah, ran into a problem where turning off Lambda auto-naming w/ Crosswalk gives us `Active stages pointing to this deployment must be moved or deleted`

that's part of the reason auto-naming is enabled by default. is there a use case for turning it off on the lambda?

We have a few internal reasons for doing so, nothing very interesting tbh. :smile:

But yeah, when using Crosswalk, autonaming is a must I suppose?

it's not necessarily a crosswalk thing, it's designed to work about these situations where the AWS resource is immutable. we build it into Pulumi for this reason

Right, gotcha. I’ll see what we can do. Appreciate the insight.