CA is not being regenerated when configured common name changes

[simskij]

Describe the bug

CA is not being regenerated when configured common name changes

To Reproduce

1. deploy this charm and relate it to something with a webserver, like traefik.
2. openssl s_client <address>
3. check CA Common Name
4. change the common name using juju config
5. wait for things to settle
6. openssl s_client <address>
7. check CA Common name

Expected behavior

for the CA, and all the certs, to be regenerated using the new CA common name

Screenshots

Logs

it says it's doing all of the things in the log, but in reality nothing changes.

unit-ssc-0: 14:57:28 INFO juju.worker.uniter.operation ran "config-changed" hook (via hook dispatching script: dispatch)
unit-ssc-0: 14:57:29 INFO juju.worker.uniter.operation ran "secret-changed" hook (via hook dispatching script: dispatch)
unit-ssc-0: 14:57:30 INFO juju.worker.uniter.operation ran "secret-remove" hook (via hook dispatching script: dispatch)
unit-ssc-0: 14:57:59 INFO unit.ssc/0.juju-log Root certificates generated and stored.
unit-ssc-0: 14:57:59 INFO unit.ssc/0.juju-log Revoked all previously issued certificates.
unit-ssc-0: 14:57:59 INFO unit.ssc/0.juju-log Generated certificate for relation 37
unit-ssc-0: 14:57:59 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-ssc-0: 14:58:00 INFO juju.worker.uniter.operation ran "secret-changed" hook (via hook dispatching script: dispatch)
unit-ssc-0: 14:58:01 INFO juju.worker.uniter.operation ran "secret-remove" hook (via hook dispatching script: dispatch)

Environment

• Charm / library version (if relevant):
• Juju version (output from juju --version):
• Cloud Environment:
• Kubernetes version (output from kubectl version --short):

Additional context