fix: add missing error returns in command handlers #656
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixed #455
This pull request fixes a recurring issue in the CLI where errors were being logged but execution continued as if nothing went wrong. In several commands, log.Errorf() was used without returning the error, which caused the CLI to proceed with invalid or empty values and fail silently.
To address this, the PR replaces error logging with explicit error returns using fmt.Errorf, ensuring that failures immediately stop execution and are correctly surfaced to the user. To support this flow, affected commands were updated to use Cobra’s RunE instead of Run, which is the recommended pattern when commands can fail.
As part of this cleanup, the unused logrus imports were removed from the affected files, since error reporting is now handled through returned errors rather than logging.
Overall, this change makes CLI behavior more predictable, prevents silent failures, and aligns error handling across commands with standard Cobra and Go best practices.