thanks @konrad.sopala !
I did that and I was able to get an answer! It’s due to the setting of an attribute: require_pushed_authorization_requests.
Even if it’s false, the inclusion of that attribute within the resource blocks causes this behavior. I believe that should be considered a bug (I filed a request at the provider repo). This attribute is OPTIONAL, hence, given this last fact, I would consider having it set to false and non-existent being the same.
@elopez : remove this attribute from the resource block you’re trying to modify (even if it’s set to false).