Charm does not detect Kubernetes secret name changes

[Ryan Finnie]

If cert_kubernetes_names is updated to change an existing cert to point to a new secret name, it appears this will not be detected and applied to the new name (but presumably would eventually once the cert comes up for renewal).

[Tom Haddon (mthaddon)]

From what I can see it detects it and configures the config file correctly (e.g. /etc/autocert/kubernetes/${sitename}.ini) but doesn't actually run the configured cert_action_cmd to update the secret. Note that if it was to do this, it would also need to track the previous secret name, and either rename it or remove the old name when creating the new one.