Specification
Currently, most of the Gestalts CLI commands do not work in isolation as they expect nodes and identities to have already been set in the Gestalt Graph. The commands will fail with an ErrorGestaltsGraphNodeIdMissing or ErrorGestaltsGraphIdentityIdMissing error, or will return no data. This is because identitiesInfoGetConnected, which is supposed to add found connected identities to the gestalt graph, is currently incomplete and is inaccessible to the CLI. (outdated)
When choosing to trust a node/identity (i.e. to send notifications/vault share), this should add the node/identity to our gestalt graph. This can be done inside the handlers for these commands. Once done, this should trigger discovery on the added node/identity.
We don't want to have to await this discovery, so the Discovery domain needs to be converted from CreateDestroy to CreateDestroyStartStop so that it can have underlying state that it can crawl in the background.
Additional context
Tasks
- Expose
identitiesInfoGetConnected to the CLI
- Implement functionality for adding trusted nodes/identities to the gestalt graph
- Add spider-crawling to the Discovery domain
- Modify/extend existing tests to match this behaviour
Specification
Currently, most of the Gestalts CLI commands do not work in isolation as they expect nodes and identities to have already been set in the Gestalt Graph. The commands will fail with an
ErrorGestaltsGraphNodeIdMissingorErrorGestaltsGraphIdentityIdMissingerror, or will return no data.This is because(outdated)identitiesInfoGetConnected, which is supposed to add found connected identities to the gestalt graph, is currently incomplete and is inaccessible to the CLI.When choosing to trust a node/identity (i.e. to send notifications/vault share), this should add the node/identity to our gestalt graph. This can be done inside the handlers for these commands. Once done, this should trigger discovery on the added node/identity.
We don't want to have to await this discovery, so the
Discoverydomain needs to be converted fromCreateDestroytoCreateDestroyStartStopso that it can have underlying state that it can crawl in the background.Additional context
Tasks
identitiesInfoGetConnectedto the CLI