Staging instance, all changes can be removed at any time

Skip to content

cli: Allow graph path parameter to be optional

Antoine R. Dumont requested to merge mr/relax-graph-path-constraint into master

If we were to run separate grpc/rpc instances, there is no need for the rpc to have access to the graph files (since that rpc would reuse the access to the other grpc instance).

Note that local rpc instance configured without any grpc instance requires the path so they can spawn internally a grpc instance (which then needs the graph files access to start).

In the current implementation, this is already possible but in one case, we need to duplicate uneeded configuration (the graph path in question).

While this is simple enough to duplicate configuration in a static environment, it's a bit more involved in a kubernetes kind of deployment (so it'd be neat if we could relax this).

The proposed implementation tries to relax the constraint and raises error when the configuration is deemed incomplete. It's improving a bit upon error messages too.

Refs. #4827

Edited by Antoine R. Dumont

Merge request reports