The resource name for this type of diff is quite long - a whole key.
You can see the string displayed on the FE below:

Do you think we could get away with not displaying the resource name for audit logs of this type, i.e. amending the description field such that it returns "description": "{user} updated git ssh key" instead of "description": "{user} updated git ssh key {target}"?

Since the private key diff value will be empty, can we omit this?

This is working great for the regenerateGitSSHKey handler as it is hit from the UI.

Is there any CLI command counterpart we need to worry about here?

If not, do you mind adjusting audit-logs.md so that we show support for GitSSHKey again?

The resource name for this type of diff is quite long - a whole key. You can see the string displayed on the FE below:

Do you think we could get away with not displaying the resource name for audit logs of this type, i.e. amending the description field such that it returns "description": "{user} updated git ssh key" instead of "description": "{user} updated git ssh key {target}"?

I think that's a good idea! I'll change that.

This is working great for the regenerateGitSSHKey handler as it is hit from the UI.

Is there any CLI command counterpart we need to worry about here?

If not, do you mind adjusting audit-logs.md so that we show support for GitSSHKey again?

CLI commands don't need to be updated, I'll add it back as well!

Since the private key diff value will be empty, can we omit this?

The idea of secret values in diffs is so we can tell a value changed without leaking that value. Maybe we can get a better way to display secret values?