Allow user to override the SQS integration

[theburningmonk]

The default integration hardcodes the MessageBody to come from the method.request.body.message. To override this I have to override the CloudFormation resource that's generated, e.g.

custom:
  apiGatewayServiceProxies:
    - sqs:
        path: /
        method: post
        queueName: {"Fn::GetAtt":[ "SQSQueue", "QueueName" ]}

resources:
  Resources:
    SQSQueue:
      Type: "AWS::SQS::Queue"

    ApiGatewayMethodPost:
      Properties:
        Integration:
          RequestParameters:
            integration.request.querystring.MessageBody: "method.request.body"

It would be good to be able to customize this, maybe along the lines of:

custom:
  apiGatewayServiceProxies:
    - sqs:
        path: /sqs
        method: post
        queueName: {"Fn::GetAtt":[ "SQSQueue", "QueueName" ]}
        messageBody: method.request.body
        cors: true

[horike37]

@theburningmonk
Thank you for the proposal!

The default integration hardcodes the MessageBody to come from the >method.request.body.message.

The default behavior may be a little strange as design. How about hardcoding method.request.body instead of method.request.body.message?
And you can override this with the messageBody parameter of serverless.yml.

This plugin still beta so it doesn't necessarily have to keep compatible.

[theburningmonk]

Ok, sounds good. Yeah, I think it makes more sense to default to method.request.body instead.

[horike37]

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀