Release v0.24.0 has broken AWS::SQS::Queue ReceiveMessageWaitTimeSeconds

[garyevari]

27150ae in #1110
has added the following definition...

{
  "op": "add",
  "path": "/ValueTypes/AWS::SQS::Queue.ReceiveMessageWaitTimeSeconds",
  "value": {
    "NumberMax": 20,
    "NumberMin": 1
  }
},

AWS official documentation found at https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-sqs-queues.html specifically states:

"Short polling is used as the default or when you specify 0 for this property"

And at https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-short-and-long-polling.html#sqs-long-polling it states:

"Short polling occurs when the WaitTimeSeconds parameter of a ReceiveMessage request is set to 0 in one of two ways:

The ReceiveMessage call sets WaitTimeSeconds to 0.

The ReceiveMessage call doesn’t set WaitTimeSeconds, but the queue attribute ReceiveMessageWaitTimeSeconds is set to 0."

Therefore, 0 is a perfectly valid value for ReceiveMessageWaitTimeSeconds and working CF definitions are now being flagged as invalid

Also, just as per the AWS Console:

[chuckmeyer]

Thanks. We have a PR in place and will drop this in a point release -- just waiting to see if anything shakes out today.

[kddejong]

Release v0.24.1 is out there and should address this.