Is there a way to customize the `sst ApolloApi` to use a cus Serverless Stack #help

Is there a way to customize the `sst.ApolloApi` to...

Dan Van Brunt

10/21/2021, 3:13 PM

Is there a way to customize the

sst.ApolloApi

to use a custom path? We’d like the root method to be at

/api

This is so that we can put the api behind a Cloundfront Distro as a reverse proxy at

<http://mydomain.com/api|mydomain.com/api>

CF origins seem to always pass the path from the front end, so there is no way to have it be

/api

on the distro and

behind the scenes. (at least without a cloudfront function) Annoying I know.

Dan Van Brunt

10/21/2021, 3:16 PM

@thdxr perhaps

sst.ApolloApi

needs a

rootRoute

property? I am curious what ApolloApi really gives you over just using

sst.Api

. Going to look at construct

Dan Van Brunt

10/21/2021, 3:23 PM

ya looks like it’s mainly to make it quicker to setup a get and post pointing to a single function. I think this could still be done with a

rootRoute

no?

routeRoute: /api

(default:

) …

Copy code

routes: {
        `GET ${routeRoute}`: server,
        `POST ${routeRoute}`: server,
      },

thdxr

10/21/2021, 3:25 PM

Yeah you can use the standard sst.Api - personally use AppSync myself as I'm not a big fan of apollo

thdxr

10/21/2021, 3:25 PM

I'm not super familiar with our ApolloApi construct one second

Dan Van Brunt

10/21/2021, 3:25 PM

I’m about to PR it to include an optional

rootRoute

as above

Dan Van Brunt

10/21/2021, 3:28 PM

I don’t think we can use AppSync as we’re doing some advanced Schema stitching using graphql-tools. But we’re just learning it now, so not entirely sure this can’t be done in AppSync. Also, I’d rather use

sst.ApolloApi

if its less code 🙂

Dan Van Brunt

10/21/2021, 3:33 PM

https://github.com/serverless-stack/serverless-stack/issues/948

Dan Van Brunt

10/21/2021, 3:38 PM

@thdxr thoughts?

thdxr

10/21/2021, 3:39 PM

Probably will let @Frank chime in since he made the original construct

Dan Van Brunt

10/21/2021, 3:43 PM

what would be even better… is a

Reroute

construct that would implement a CF Function to do nothing more but reroute

from

to

by attaching a FunctionAssociation to a behavior. eg…

Copy code

new Reroute(this, {
  behavior,
  from: '/api/*',
  to: '/*'
})

🙂

Dan Van Brunt

10/21/2021, 3:44 PM

then you wouldn’t need this change.

Dan Van Brunt

10/21/2021, 3:52 PM

hmmm may try this. ☝️

Frank

10/21/2021, 5:17 PM

Hey @Dan Van Brunt, having a

rootRoute

option makes sense. I might call it just

route

Frank

10/21/2021, 5:17 PM

I will take a look at the issue today.

Frank

10/21/2021, 5:19 PM

Reroute

is interesting idea too.. but having a

route

option seems more straight forward in this case.

Dan Van Brunt

10/21/2021, 6:24 PM

@Frank understood. just didn’t want

route

to be confused with

sst.Api

’s

routes

route

would only be the string route and not the method or anything else.

Dan Van Brunt

10/21/2021, 6:24 PM

I’ll see what I can get in.

Dan Van Brunt

10/21/2021, 7:26 PM

@thdxr https://github.com/serverless-stack/serverless-stack/pull/950

Frank

10/21/2021, 9:38 PM

Thanks @Dan Van Brunt! Ur suggestion on the naming makes a lot of sense. Between

rootRoute

and

rootPath

, which do u prefer? I lean towards

rootPath

more.

Dan Van Brunt

10/21/2021, 10:21 PM

yup… rootPath makes sense

Dan Van Brunt

10/21/2021, 10:22 PM

want me to adjust?

Frank

10/21/2021, 10:22 PM

That’d be awesome!

Frank

10/21/2021, 11:49 PM

Thanks @Dan Van Brunt Will get this merged asap.

Open in Slack

Previous Next