NorskManager.publishDiscoveryFleet() method
Publish the deployment’s discovery fleet: every replica’s address, the leaf token, and the tier secret node tokens are minted from. The Manager keeps it and sends each connected node, and each node at its hello, its own access (every replica address, the leaf token and a node token minted for it); the tier secret never reaches a node. Refused (INVALID_ARGUMENT) when the tier secret is empty or equals the leaf token, or an address is not host:port.
The first tier secret and leaf token published STAY IN FORCE: a later publish carrying different ones keeps them, and the reply says so (secretsKept) and returns the ones in force, which the caller adopts. addresses is protocol 1.7; a fleet with none and an address is the single server of 1.4.
Signature:
publishDiscoveryFleet(fleet: {
address?: string;
addresses?: string[];
token: string;
tierSecret: string;
}): Promise<{
forwardedTo: number;
tierSecret: string;
tierSecretAlt: string;
token: string;
secretsKept: boolean;
}>;