Markus Bergholz

@jpiron sorry for the late reply, I was out of office. > Shouldn't the module perform an `INSERT` if the `get_config` returns `False` ? That might work I think. Are...

> That might work I think. Are we sure that there are not side-effects when inserting new global variables to proxysql? I've inserted a random name variable. It looks like...

@willska sorry for the late reply. can you also add a changelog fragment please?

> @markuman can we merge this and add the fragment ourselves? I could or you can if you want yes, let's do it. After you've added the changelog fragment, we...

`proxysql_scheduler` search for the entry with ```sql SELECT count(*) AS `schedule_count` FROM scheduler WHERE active = %s AND interval_ms = %s AND filename = %s""" ``` so when you request...

True. And update a scheduler task happens only when an `id` is provided. But it would be helpful if we provide a `proxysql_scheduler_info` module to determine ids.

>> And update a scheduler task happens only when an id is provided. > or when a user defined it originally (is it possible to set it when creating the...

Do we still need a `proxysql_scheduler_info` module? Because `proxysql_info` exists since 1.2.0 ```yml - name: Add a schedule community.proxysql.proxysql_scheduler: login_user: 'admin' login_password: 'admin' interval_ms: 1000 filename: "/opt/maintenance.py" state: present load_to_runtime:...

[here](https://github.com/ansible-collections/community.proxysql/issues/23#issuecomment-883621834) we discussed the behaviour of adding or updating schedule tasks and decided to fallback to a new `id` parameter for updates. So far so good. Say now, we ended...

> id is mutually exclusive with all other parameters when state is absent. is this possible?