Charmed MySQL

Learn about configurations >

• binlog-retention-days | int

  Default: 7

  Number of days for binary logs retention

• cluster-name | string

  Optional - Name of the MySQL InnoDB cluster, set once at deployment

• cluster-set-name | string

  Optional - Name for async replication cluster set, set once at deployment. On recreate-clster action call, the cluster set name will be re-generated automatically.

• logs-audit-policy | string

  Default: logins

  Audit log policy. Allowed values are: "all", "logins" (default), "queries". Ref. at https://docs.percona.com/percona-server/8.4/audit-log-plugin.html#audit_log_policy

• logs-retention-period | string

  Default: auto

  Specifies the retention period for rotated logs, in days. Accepts an integer value of 3 or greater, or the special value "auto". When set to "auto" (default), the retention period is 3 days, except when COS-related, where it is 1 day

• max-connections | int

  Maximum number of connections allowed to the MySQL server. When set max-connections value take precedence over the memory utilization against innodb_buffer_pool_size.

• pause-after-unit-refresh | string

  Default: first

  Wait for manual confirmation to resume refresh after these units refresh Allowed values: "all", "first", "none"

• plugin-audit-enabled | boolean

  Default: True

  Enable the audit plugin

• plugin-audit-strategy | string

  Default: async

  Audit log plugin strategy. Allowed values are: "semi-async" and "async". Ref. at https://docs.percona.com/percona-server/8.4/audit-log-plugin.html#audit_log_strategy

• profile | string

  Default: production

  profile representing the scope of deployment, and used to be able to enable high-level customisation of sysconfigs, resource checks/allocation, warning levels, etc. Allowed values are: “production” and “testing”.

• profile-limit-memory | int

  Amount of memory in Megabytes to limit MySQL and associated process to. If unset, this will be decided according to the default memory limit in the selected profile. Only comes into effect when the production profile is selected.

• tls-client-private-key | secret

  A Juju secret URI of a secret containing the private key for client-to-server TLS certificates. The private key must be PEM formatted, base64 encoded and at least 2048 bits long.

• tls-peer-private-key | secret

  A Juju secret URI of a secret containing the private key for peer-to-peer TLS certificates. The private key must be PEM formatted, base64 encoded and at least 2048 bits long.