@jordanpadams

What is says is semi accurate and precise. If you wish different text, then tell me what text you want it to say.

Should also change -es too as part of cleanup. Give me a list of old/new and we can change them all.

@al-niessner

Old:

-es <url>         Elasticsearch URL. Default is app:/connections/direct/localhost.xml

New:

-es <uri>         File URI to the configuration to connect to the OpenSearch Registry. For example, file:///home/user/.pds/mcp.xml. Default is app:/connections/direct/localhost.xml

Let's keep it -es because I don't think it is worth introducing a backwards incompatible change. If we really want to button this up, then:

-es <uri>         (deprecated) File URI to the configuration to connect to the OpenSearch Registry. For example, file:///home/user/.pds/mcp.xml. Default is app:/connections/direct/localhost.xml

-registry <uri>         (deprecated) File URI to the configuration to connect to the OpenSearch Registry. For example, file:///home/user/.pds/mcp.xml. Default is app:/connections/direct/localhost.xml

@tloubrieu-jpl thoughts?

Hi @jordanpadams , @al-niessner ,

I am good with option 2 with both -es and -registry (not deprecated though, compared to Jordan's comment above). I like the -registry because we could think of enriching the xml connection file, adding other databases (e.g. graphDB, ...) that harvest would update, if that is a route we want to take.