Checked for duplicates

Yes - I've already checked

🧑‍🔬 User Persona(s)

Node Operator, Data Engineer

💪 Motivation

...so that I can use a consistent CLI interface across harvest and registry-manager without having to supply separate connection and auth flags, reducing configuration complexity and the chance of misconfiguration.

📖 Additional Details

Currently the two tools have diverged in how configuration is supplied:

harvest (current):

harvest -c /path/to/registry-harvest-config.xml

Auth is parsed automatically from the XML config file.

registry-manager (current):

registry-manager <command> -registry file:///path/to/registry-harvest-config.xml -auth /path/to/auth.txt

Auth must be supplied separately via a dedicated -auth flag.

Requested changes to registry-manager:

1. Add a -c flag that accepts the config XML path (matching harvest behavior)
2. When -c is used, parse the auth file location from the XML (just as harvest already does)
3. Deprecate -registry and -auth flags — keep them functional but print a deprecation warning when used
4. Apply to all registry-manager sub-commands that currently accept -registry/-auth

This alignment will make both tools feel like a coherent suite and lower the learning curve for operators who use both.

For Internal Dev Team To Complete

Acceptance Criteria

Given a registry-manager command that currently requires -registry and -auth
When I perform the same command using -c /path/to/config.xml
Then I expect registry-manager to connect and authenticate using values parsed from the XML, identical to how harvest behaves

⚙️ Engineering Details

🎉 I&T