Serverless Stack

When I add a route to an `sst.WebSocketApi` that uses a Lambda integration, the source ARN of the API Gateway trigger that gets added to the Lambda function appears to be incorrectly formatted

The API Gateway routes get configured with the correct Lambda integrations, and the Lambdas get the correct Permissions added. It seems to just be an issue with the Trigger itself, so I think the correct functionality should be maintained, but better safe than sorry.

Hey <@U03499GEQQG>, hmm… the source ARN seems to match in both screenshot?

But shouldn't it be `.../*/$connect` instead of including that second asterisk?

ah yeah.. seems to come from here <https://github.com/aws/aws-cdk/blob/7966f8d48c4bff26beb22856d289f9d0c7e7081d/packages/%40aws-cdk/aws-apigatewayv2-integrations/lib/websocket/lambda.ts#L35|https://github.com/aws/aws-cdk/blob/7966f8d48c4bff26beb22856d289f9d0c7e7081d/packa[…]40aws-cdk/aws-apigatewayv2-integrations/lib/websocket/lambda.ts>

`…/*/*$connect` should also works right?