Does `sst.API` support <Service Integrations> or s...
# help
d
Does
sst.API
support Service Integrations or should we be using CDK’s
apigw.RestApi
?
assuming no, since the methods need explicitly a function. Also curious if anyone knows if its possible to setup an authorizer and an service integration on
apig.restApi
d
d
@Derek Kershner yup, very aware of this construct. Not sure if it supports Service Integrations though.
I believe the answer is there, behind the "AWS services" line item
never used myself, though
d
@Derek Kershner The word “service” doesn’t appear on the SST ApiGatewayV1Api docs anywhere. Where are you seeing the details of if it supports Service Integrations?
its in the "Integrations" table
d
Those are AWS docs. I know CDK’s
@aws-cdk/aws-apigateway
supports Service Integrations, we are using them now… but my question is “Does
sst.ApiGatewayV1Api
support them?”
d
they are the same construct behind the scenes, you can access the apiG itself on a prop
d
sure but the base construct requires you to pass in “Functions” “routes” of which I will have none of
so I guess it makes no sense to even use
sst.ApiGatewayV1Api
and just use
@aws-cdk/aws-apigateway
+
sst.Function
d
if you arent going to use SST functionality, id agree.
if you do want to, you can just access
api.httpApi
, and do all of the same things you would have in the CDK stack.
d
if I’m using
sst.Function
either way…. what else sst would I loose… considering I’m also not using the route helpers.
d
the ability to run the functions locally
d
Isn’t that built into
sst.Function
?
d
well, I guess so long as you use
sst.Stack
,
<http://sst.App|sst.App>
,
sst.Function
, and you just want to invoke rather than use APIG's body event, you lose nothing
d
woot
thats what I’m planning
Thanks @Derek Kershner