What I did was lookup if a key exists before generating: IPFS Documentation | IPFS Docs
But it’s true that I (re)generated the key at different nodes using the same input parameters.
So there’s only one way to publish at multiple nodes behind a load balancer at the moment:
- Manual copy of keystore file
It’s an easy job, but not when you run a lot of domains at the nodes. So it would be nice if sharing keystores could be automated.
key/pull?arg=<name>&peer=<peerid_of_node>
Or send a custom peer id to the existing generate endpoint:
key/gen?arg=<name>&peer=<peerid_of_other_node>
But that’s what you aswered here, right?
Correct. Right now you can only publish to PeerID of your Identity key.
Support for publishing to alternative key is planned, but not implemented yet (v0.4.8-DEV):
.