WAFv2 AndStatement and OrStatement incorrect validation

Hi guys,

https://github.com/cloudtools/troposphere/blob/f287fa8999ef2a5f5e301ba5c0af6421471e230b/troposphere/validators/wafv2.py#L32-L33

In the validator for WAFv2 statements, there is a check to see if the number of statements if exactly 2 when it should be looking to see if there are at least 2 statements given.

“You provide more than one Statement within the AndStatement.” Source

AWS requires there to be more than one statement, but does not restrict them to only pairs.

A small change in the logic of the if statement and the TypeError message is all that is needed.

Thank you

[markpeek]

Fixed in Release 4.0.1

[MattJaccino]

Had to rework the pieces on our end around the creation of the resources, but definitely nice to have all of the features available now.

Not specific to WAFv2, but one thing that did strike me as odd was that resource objects can be successfully initialized without all of the required properties being given. I thought I remembered it erroring out in situations like that, or am I missing something. ?

I thought with a property defined as

class SomeProperty(AWSProperty):
    props: PropsDictType = {
        "Prop1": (TYPE, True),
        "Prop2": (TYPE, False),
    }

if you tried to initialize without defining Prop1, it would throw some kind of exception. It seems like you can initialize resource objects without including all of the required properties, or with none at all.

Was this always the case, or did something change? If not, could that potentially be a feature request?

Thank you man