I’m having an issue where I created an AppSyncApi in one project, and am trying to extend it in another project (ie, add resolvers) by importing the GraphQL like the example:

import { GraphqlApi } from "@aws-cdk/aws-appsync-alpha";

const api = new AppSyncApi(this, "GraphqlApi", {
  graphqlApi: GraphqlApi.fromGraphqlApiAttributes(this, "IGraphqlApi", {
    graphqlApiId,
  }),
});

However, if i then try to add a unit resolver where i reference a datasource I added in the first stack it fails; also, if i try to lookup the datasource by name

api.getDataSource('mydsName');

it also returns undefined. Any thoughts?

Hm @Frank do we support importing like this?

I think it should be this, if it behaves like CDK:

const api =  GraphqlApi.fromGraphqlApiAttributes(this, "IGraphqlApi", {
    graphqlApiId,
  });

That's not the problem. The problem is getting access to the data source which is needed when you add a resolver.

Yeah the issue is when you import it we don't know anything about sst specific concepts so we're not hydrating those fields. Idk if this is supported right now

I don't know if it's even possible in CDK. It's like you can only add the resolvers in the same context as where you add the data source.

You can add resolvers lazily but it needs to be within the same project

Sorry for the late follow up guys. @Guy Shechter just to clarify, the data source

mydsName

is not created in this

AppSyncApi

construct right?

That's what I was hoping yes. It's attached in a different construct.

Is that construct in the same SST app?

No

I see. Yeah there doesn’t seem to be an easy to import existing data sources.