ariatosca-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARIA-138) CLI output verbosity levels
Date Thu, 20 Apr 2017 12:08:04 GMT


ASF GitHub Bot commented on ARIA-138:

Github user mxmrlv commented on a diff in the pull request:
    --- Diff: aria/cli/commands/ ---
    @@ -161,11 +170,13 @@ def start(workflow_name,
    -def _cancel_execution(workflow_runner, execution_thread, logger):
    +def _cancel_execution(model_storage, workflow_runner, execution_thread, logger):'Cancelling execution. Press Ctrl+C again to force-cancel')
    +    log_iterator = cli_logger.ModelLogIterator(model_storage, workflow_runner.execution_id)
    --- End diff --
    use existing

> CLI output verbosity levels
> ---------------------------
>                 Key: ARIA-138
>                 URL:
>             Project: AriaTosca
>          Issue Type: Story
>            Reporter: Maxim Orlov
>            Assignee: Maxim Orlov
> The CLI should support the display of the following logging levels:
> default: execution logs: simple representation of executed operations
> -v      : execution logs: representation with time stamps and logging levels
> -vv    : execution logs: retrieve the stacktrace of any failed operation.
> -vvv  : all configured loggers should be set to {{debug}} level; any CLI errors should
be logged and printed with their stack trace as well.
> (both the default and the first level of logging format should be configurable). 
> Note that all of the operations logs should be saved in the storage. This issue relates
only to the way the logs are displayed in the CLI.

This message was sent by Atlassian JIRA

View raw message