Fix SQS QueueUrl transformation to ARN when intrinsic function being passed in

[FilipPyrek]

Should solve: #253

I got an idea that maybe it would be nice if we could set QueueArn in State Machine definition like this:

some-step:
  Type: Task
  Resource: arn:aws:states:::sqs:sendMessage.waitForTaskToken
  Parameters:
    QueueUrl: { "Fn::ImportValue": "some-queue-url" }
    QueueArn: { "Fn::ImportValue": "some-queue-arn" }
    Message: "42"
  End: true

But I wasn't sure how this would fit to architecture of whole project.

[theburningmonk]

Doesn't look like Step Functions supports QueueARN for the SQS integration. If you did that, you'd have to translate the ARN into a queue URL. I'm not seeing the value of that, got any use case in mind?

[theburningmonk]

ah, now I see why you want to add both QueueUrl as well as QueueArn, so you can ref the Arn in the IAM instead of QueueUrl. It'd be doable for sure, but it'd be a bit odd though, and hard to explain to people. Let's leave it as it is for now.

[FilipPyrek]

Yeah, that's what I meant. I agree with you. 🙂 👍

[theburningmonk]

LGTM

[theburningmonk]

🎉 This PR is included in version 2.8.2 🎉

The release is available on:

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

Your semantic-release bot 📦🚀