Hey @tyf : yup, I became aware of that attribute being the culprit and removed it a couple of hours ago. Do you know where we can find documentation explaining these sort of scenarios?
++ I filed a bug a couple of hours ago explaining the expectation around an optional attribute (of having it set in the resource block with a false value and omitting it having the exact same result)