community.proxysql.proxysql_scheduler – Adds or removes schedules from proxysql admin interface
Note
This plugin is part of the community.proxysql collection (version 1.3.0).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install community.proxysql
.
To use it in a playbook, specify: community.proxysql.proxysql_scheduler
.
Synopsis
The community.proxysql.proxysql_scheduler module adds or removes schedules using the proxysql admin interface.
Requirements
The below requirements are needed on the host that executes this module.
PyMySQL
mysqlclient
Parameters
Parameter |
Comments |
---|---|
A schedule with active set to Choices:
|
|
Argument that can be passed to the job. |
|
Argument that can be passed to the job. |
|
Argument that can be passed to the job. |
|
Argument that can be passed to the job. |
|
Argument that can be passed to the job. |
|
Text field that can be used for any purposed defined by the user. |
|
Specify a config file from which login_user and login_password are to be read. Default: “” |
|
Full path of the executable to be executed. |
|
By default we avoid deleting more than one schedule in a single batch, however if you need this behaviour and you are not concerned about the schedules deleted, you can set force_delete to Choices:
|
|
How often (in millisecond) the job will be started. The minimum value for interval_ms is 100 milliseconds. Default: 10000 |
|
Dynamically load config to runtime memory. Choices:
|
|
The host used to connect to ProxySQL admin interface. Default: “127.0.0.1” |
|
The password used to authenticate to ProxySQL admin interface. |
|
The port used to connect to ProxySQL admin interface. Default: 6032 |
|
The socket used to connect to ProxySQL admin interface. |
|
The username used to authenticate to ProxySQL admin interface. |
|
Save config to sqlite db on disk to persist the configuration. Choices:
|
|
When Choices:
|
Examples
---
# This example adds a schedule, it saves the scheduler config to disk, but
# avoids loading the scheduler config to runtime (this might be because
# several servers are being added and the user wants to push the config to
# runtime in a single batch using the community.general.proxysql_manage_config
# module). It uses supplied credentials to connect to the proxysql admin
# interface.
- 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: False
# This example removes a schedule, saves the scheduler config to disk, and
# dynamically loads the scheduler config to runtime. It uses credentials
# in a supplied config file to connect to the proxysql admin interface.
- name: Remove a schedule
community.proxysql.proxysql_scheduler:
config_file: '~/proxysql.cnf'
filename: "/opt/old_script.py"
state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
The schedule modified or removed from proxysql. Returned: On create/update will return the newly modified schedule, on delete it will return the deleted record. Sample: {“changed”: true, “filename”: “/opt/test.py”, “msg”: “Added schedule to scheduler”, “schedules”: [{“active”: “1”, “arg1”: null, “arg2”: null, “arg3”: null, “arg4”: null, “arg5”: null, “comment”: “”, “filename”: “/opt/test.py”, “id”: “1”, “interval_ms”: “10000”}], “state”: “present”} |
Authors
Ben Mildren (@bmildren)