Markus Bergholz

@mrpk1906 Do you some time to dive in and help here?

Well, there is a parameter already. blame me. `encrypt_password:` the only question left is, if we should/can fix the behaviour above, and detect if the unterlying password is hashed already.

Ok, the error persists when I use in the last task from the example above `encrypt_password: yes` ```yml - name: idempotent add user to proxysql proxysql_mysql_users: state: present username: someuser...

Using only `encrypted_password: yes` works perfectly. There is no need to use the [workaround](https://proxysql.com/documentation/password-management/) when you're already using community.proxysql. When you do the workaround, `proxysql_mysql_users` will fail. Imo, we should...

due lack of time, nothing happen here. but another idea for the future is to use the api of proxysql instead of SQL. https://github.com/sysown/proxysql/tree/a443e3ded055088bde7594eb52d9050c23c5f32e/scripts#query-the-endpoints

It's not compatible with `proxysql_manage_config`, because it required 4 parameters, but we need only 3 parameters. I can think of 2 options 1. Implement `community.proxysql.proxysql_query` and use it to query...

yes, this is working fine. ```yml - name: reload proxysql tls certificates community.mysql.mysql_query: login_user: admin login_password: admin login_port: 6032 query: PROXYSQL RELOAD TLS; register: out ``` results in ``` "out":...

> If a specialist reviews, tests, and provides feedback that the c.proxysql users will get what they expect, we could merge the module > > @markuman if you could take...

> > If a specialist reviews, tests, and provides feedback that the c.proxysql users will get what they expect, we could merge the module > > @markuman if you could...

> We can open a feature request issue for oauth2 and I or perhaps someone from the community could help out adding it. That would be awesome!