Creating ssh key in a shared vault should generate warning

A warning would be good, but I had a very good reason for creating an SSH in a shared vault today: we’re putting it in an external system. The only thing I’m not 100% happy about is that the way that it was exported doesn’t appear to be compatible with Jenkins (I think that the private key copy is different than what can be obtained with op).

We'll have a (better) warning in very soon, and support for using keys in other vaults will follow.

@austin About Jenkins, which key format is the culprit? The one you get in op or the one you get when copying it in the GUI?

It’s not the key format. It’s Jenkins. It doesn’t know how to deal with ed25519 keys, yet.

@rodneyt @austin
I wanted to let you know that we're working on a solution that allows for the following:
- Enable keys from other vaults than the Private vault.
- Create isolated setups with certain keys offered on a separate socket.
- Control the order in which keys are offered to SSH servers.
It would be great to get your feedback on our proposal, if you're (still) interested. You can do so by joining the #ssh-agent-config channel in our Slack workspace.