[ https://issues.apache.org/jira/browse/ARIA-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976562#comment-15976562 ]
ASF GitHub Bot commented on ARIA-138: ------------------------------------- Github user mxmrlv commented on a diff in the pull request: https://github.com/apache/incubator-ariatosca/pull/104#discussion_r112436004 --- Diff: aria/orchestrator/workflows/core/engine.py --- @@ -40,6 +40,7 @@ class Engine(logger.LoggerMixin): def __init__(self, executor, workflow_context, tasks_graph, **kwargs): super(Engine, self).__init__(**kwargs) + self.logger.addHandler(logger.NullHandler()) --- End diff -- ??? > CLI output verbosity levels > --------------------------- > > Key: ARIA-138 > URL: https://issues.apache.org/jira/browse/ARIA-138 > 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 (v6.3.15#6346)