Comment 1 for bug 1611711

This should be fixed before we release 2.0.

FWIW, I think this may have been caused by poor naming in the @operation decorator: it takes a boolean argument "idempotent" which then exposes the operation via HTTP GET when idempotent is True or POST when False. However, mutations should always be done via HTTP POST, whether idempotent or not.