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

So here's an architectural question I've got with Pulumi, and I'd love some thoughts on it.

When you use AWS API Gateway, your calls to the AWS API make stateful changes to the gateway's configuration. However, it also has the concept of a "deployment", which has to be bumped in order to actually push those changes live. Because Pulumi and not AWS's state is the canonical record for me, I would like a deployment to be bumped each and every time I make a change to a method, an integration--whatever.

Is there a good way to express this in Pulumi? I'm struggling to think of one.

There is a standard "trick" to this that every tool that automatoes API Gateway creation reinvents (Serverless Framework, Pulumi, others) because the underlying resource model in AWS is awkward for IAC.

You can see how this is done in `awsx` to provide a simple approach to API Gateway here:  <https://github.com/pulumi/pulumi-awsx/blob/e709a077df4233eef0615bad09d0f6828e50f2bd/nodejs/awsx/apigateway/api.ts#L369-L383>