Unable to update appsync which are created manually.

[pradheepap]

Hi,

Does the plugin only supports appsync created through serverless?
Is there a way where in we can update the appsync which are created manually or by other CDK scripts.

Thanks!
Regards
Pradheepa

[liuhx1027]

we have the similar requirement that our appsync instance was created by other terraform stack which also creates CloudFront and link them together. is there any way to change the existing appsync instance instead of creating a new one?

[bboure]

This is a topic that has been discussed in the past.

There is not an easy solution.
Please see this comment

If someone wants to have a look at this and give it a try, maybe it is worth it.

[sid88in]

This is the same theme as #300 and the broader "existing API" discussion. Two things are
bundled here:

1. Attaching resolvers/data sources to an existing API by id (including one created by
   Terraform/CDK): not possible on the current v2 release, but being re-added in feat: add support for multiple cloudformation stacks (Add apiId) #647 (draft),
   which brings back an apiId option. Since resolvers attach by apiId, that path doesn't
   care what created the API. Follow feat: add support for multiple cloudformation stacks (Add apiId) #647 for this.

2. Having the plugin manage/update the API's own definition (auth, schema, logging) when
   it's owned by Terraform/CDK: that isn't something apiId does — it adds child resources,
   it doesn't take over the parent API. Bringing a foreign-created resource under
   CloudFormation management needs CloudFormation's "import existing resources" workflow,
   which is an AWS-level operation outside this plugin.

Closing as a duplicate of #300 and linking #647 for the resolvers/data-sources part. Thanks
@pradheepa, @liuhx1027.