Currently, a migration runs and adds the users and passwords based on what is mounted to /run/secrets/users at the time. A better solution would hash the secrets when set, and then compare that to a hash of the current secret. It could then update the credentials if the hashes are different.
Currently, a migration runs and adds the users and passwords based on what is mounted to /run/secrets/users at the time. A better solution would hash the secrets when set, and then compare that to a hash of the current secret. It could then update the credentials if the hashes are different.
Could store the hashes in the migration volume.