Issue:
When using dignode remote sync seed, there may be a circumstance where the config has not yet recorded a remote IP address for the dig server.
Expected behavior:
As a user I would expect to be promted to enter the dig server IP if it is not present when issueing the dignode remote sync seed command.
Current Behavior:
As a user I ran dignode remote sync seed and received error. Manually editing the dig.config .json with the appropriate server IP seems to bypass the issue. This requires the user to be aware of this issue to address at the moment of use.
Issue:
When using
dignode remote sync seed, there may be a circumstance where the config has not yet recorded a remote IP address for the dig server.Expected behavior:
As a user I would expect to be promted to enter the dig server IP if it is not present when issueing the
dignode remote sync seedcommand.Current Behavior:
As a user I ran
dignode remote sync seedand received error. Manually editing the dig.config .json with the appropriate server IP seems to bypass the issue. This requires the user to be aware of this issue to address at the moment of use.