CLI continues execution after log.Errorf() instead of returning error

[AnvayKharb]

In multiple Harbor CLI commands, when an error occurs it is logged using log.Errorf() but the function does not return the error. Execution continues after the error, causing variables like projectName, repoName, or reference to be empty or invalid.

Because of this, the command does not fail immediately and instead proceeds with incorrect state, leading to silent failures and confusing downstream behavior. The CLI appears to run successfully even though a critical error has already occurred.

[AnvayKharb]

#656

[DhruvTotala]

Thanks for working on this — the direction looks solid

While working on issue #655, I explored a similar fix locally and noticed a couple of additional cases where execution could still continue after an error. In my approach, I addressed this by consistently converting affected commands to RunE, returning errors instead of logging them, and removing os.Exit() usage to allow proper error propagation.

Happy to share specific suggestions or patches if that’s helpful. Let me know — I’d be glad to collaborate on this.

My PR Link :- #659

[samruddhi-Rahegaonkar]

@qcserestipy I'd like to help shape a consistent error handling strategy for this CLI. My PR shows an initial example. I can help identify other commands with similar patterns, propose shared helpers, and formalize guidelines for error vs logging behavior.