I would suggest also adding an output of the public key at the end or a success log with the key path
what do you think?

The rspamd version supports this AFAIK.

Nobody is interested in contributing changes to these existing two scripts for DKIM AFAIK, it's better to replace them with the single keypair generation method I've proposed using smallstep step-cli. You'll find that supports the public key output too.

I'll tackle that for v15 release, I need to first wrap up a task unrelated to DMS before I can come return to DMS LDAP PR work (docs + refactor). The docs are blocking on v14 so hopefully I can sort that out by the weekend 😅

As for key path, not that important. New approach will have a predictable location and storage convention for the DMS config volume. Those will be copied to an internal location in DMS at runtime with config generation handled.