(aws-apigateway): Allow for custom authorizer context in StepFunctionsIntegration

[rogerchi]

Description

Currently there's no option to output custom authorizer context values into the express step function integration. The only available option is to include the single authorizerPrincipalId field in requestContext. A possible change would be to add authorizer: boolean into StepFunctionsRestApiProps which would output the full $context.authorizer object in a authorizer: {} object in the input to the state machine.

Use Case

A common use case for custom authorizers is to set custom context values and use them downstream in the integration. This change would allow them to be used in a step functions integration.

Proposed Solution

Add authorizer: boolean to StepFunctionsExecutionIntegrationOptions
Add const includeAuthorizer = options.authorizer ?? false; and templateStr = templateStr.replace("%INCLUDE_AUTHORIZER%", String(includeAuthorizer)); to templateString() in stepfunctions.ts
Add

#set($includeAuthorizer = %INCLUDE_AUTHORIZER%)

and

    #if ($includeAuthorizer)
        #set($inputString = "$inputString, @@authorizer@@:{")
        #foreach($paramName in $context.authorizer.keySet())
            #set($inputString = "$inputString @@$paramName@@: @@$util.escapeJavaScript($context.authorizer.get($paramName))@@")
            #if($foreach.hasNext)
                #set($inputString = "$inputString,")
            #end
        #end
        #set($inputString = "$inputString }")
    #end

to stepfunctions.vtl template.

Other information

No response

Acknowledge

• I may be able to implement this feature request
• This feature might incur a breaking change

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.