Modified datasource types don't get updated correctly

[nthornton2010]

When a datasource type is changed, it doesn't deploy correctly until the datasource's name is changed.

For example, I had 2 datsources that were both type AWS_LAMBDA but decided to go a different direction with both. 1 was updated to be type HTTP and the other type NONE. Neither of these started working until the datasource's name changed. The same happens when switching a non AWS_LAMBDA type to AWS_LAMBDA as well.

[nthornton2010]

After further testing this morning, it looks like changing the data source's name doesn't always fix the issue. Sometimes the field needs to be manually removed from the schema and the original data source has to be manually deleted (both from the AWS console) before deploying. This behavior also causes issues with rolling back a deployment because you'd be switching types to go back which would also cause a simple rollback to break.

[nthornton2010]

This might be related to the other issue I reported: #394

[nthornton2010]

Based on the following comment from an AWS dev in a related issue and the source code for this plugin, I no longer believe this is an issue with this plugin but a design flaw in AppSync itself so I'm closing the issue. I say design flaw and not a bug because they say it's by design (a terrible design in my opinion).

aws/aws-appsync-community#146 (comment)