# mysql\_user pure

**URL:** <https://forum.ansible.com/t/mysql-user-pure/13740>\
**Category:** Ansible Developer\
**Created:** [October 22, 2013, 9:47am UTC](https://forum.ansible.com/t/mysql-user-pure/13740 "2013-10-22T09:47:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Petrus\_Rademeyer](https://avatars.discourse-cdn.com/v4/letter/p/ec9cab/32.png) [@Petrus\_Rademeyer](https://forum.ansible.com/u/Petrus_Rademeyer)\
**Post date:** [October 22, 2013, 9:47am UTC](https://forum.ansible.com/t/mysql-user-pure/13740/1 "2013-10-22T09:47:12Z")

</div>

I’m reposting this on here from the github issue ([https://github.com/ansible/ansible/issues/4615](https://github.com/ansible/ansible/issues/4615))

---

<div class="post-metadata">

**Author:** ![James\_Cammarata1](https://avatars.discourse-cdn.com/v4/letter/j/d26b3c/32.png) [@James\_Cammarata1](https://forum.ansible.com/u/James_Cammarata1)\
**Post date:** [October 22, 2013, 1:46pm UTC](https://forum.ansible.com/t/mysql-user-pure/13740/2 "2013-10-22T13:46:23Z")

</div>

The existing module should be extended to transparently fallback to using the client directly. This is typically done with some try/except blocks at the top of the file which set flags for later use - dig around in some of the other modules for examples.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [October 22, 2013, 1:56pm UTC](https://forum.ansible.com/t/mysql-user-pure/13740/3 "2013-10-22T13:56:12Z")

</div>

See also the module development page on the main docs site too!

– Michael