Skip to content

Optionally return a different exit code when fail-on-error=false and there are errors #97

@bbandlamudi

Description

@bbandlamudi

This is also requested by @lsaishanker - This is not a must feature as the workaround is developers can get a line count of error file provided they defined one using the option ERROR-FILE-NAME.

If fail-on-error=false, corb currently do not distinguish from the errors from successful transactions. There should be an option to return a different exit code (if not set, return 0 as usual) when there is more than 1 error.

Also, it would be useful to track/print the count of errors as part of regular status messages.

There is no easy way to get the final count of errors to calling script as we can't shove that info exit code, but that would be ok. The developers can write errors to a file and count from there.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions