Serverless Stack

It looks like when updating the resolver data source in the appsync construct you have to remove it, deploy, add it back, and redeploy. Changing the data source does not result in an update.

Oh I see. Do you have a snippet of what it was set to before and after?

Hey sorry for the late reply.  It’s going from lambda resolver to vtl

From
``` "Query license": "mainDS",```
To:
```"Query license":  {
                dataSource: "dynamoDS",
                resolverProps: {
                    requestMappingTemplate: MappingTemplate.fromFile("src/mapping-templates/Query.license.req.vtl"),
                    responseMappingTemplate: MappingTemplate.fromString("$utils.toJson($context.result)")
                }
            }```

Thanks man! Was tied up yesterday with the Python release. I’m going to take a look at this today.

Hey <@U01PENBR2CW>, I had a chance to dig into this. It seems to be a known AppSync/Amplify issue. Here’s a link to the discussion - <https://github.com/aws/aws-cdk/issues/13269>

Apparently this issue has been around for years?! Removing and recreating the GraphQL API works, but that doesn’t make sense for production usage. The Amplify community seems to suggest this workaround - <https://github.com/aws-amplify/amplify-cli/issues/682>

<@U01JVDKASAC> I did end up finding a fix for this.
<https://github.com/serverless-stack/serverless-stack/pull/418>

Oh nice! I’m going to cut a release with this today.

Released this in <https://github.com/serverless-stack/serverless-stack/releases/tag/v0.26.0|v0.26.0>