[api-gateway] RestApi construct does not automatically create new deployments after addGatewayResponse

[keabarnes]

When calling the addGatewayResponse method on a RestApi, any GatewayResponse added doesn't come into effect because it doesn't trigger a new deployment. Manually creating a new deployment through AWS UI fixes this.

Similar to #8024
Related: #5354 (comment)

Reproduction Steps

First deploy:

    const restApi = new RestApi(this,"MyRestApi");

    const restNotes = restApi.root.addResource("notes");
    restNotes.addMethod(HttpMethod.GET, ...);

Subsequent deploy:

    const restApi = new RestApi(this,"MyRestApi");

    restApi.addGatewayResponse("4xxGatewayResponse", {
      type: ResponseType.DEFAULT_4XX,
      responseHeaders: {
        "Access-Control-Allow-Origin": "'*'",
        "Access-Control-Allow-Headers": "'*'",
      },
    });

    const restNotes = restApi.root.addResource("notes");
    restNotes.addMethod(HttpMethod.GET, ...);

What did you expect to happen?

A change in the GatewayResponse for an API should trigger a deployment, as that's what's required when using the UI.

What actually happened?

No new deployment was created when the GatewayResponse resource was changed.

Environment

• CLI Version :1.51.0
• Framework Version: 1.53.0
• Node.js Version: 10.16.3
• OS : MacOS
• Language (Version): TypeScript (3.9.6)

---

This is 🐛 Bug Report

[keabarnes]

I haven't had the time to create a minimal reproduction of the error and have only observed this issue through debugging of my current project.

[nija-at]

Thanks for reporting. The fix is posted here - #11068

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.