Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id F1C25200C75 for ; Sun, 21 May 2017 11:07:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E5153160BD0; Sun, 21 May 2017 09:07:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3E285160BA4 for ; Sun, 21 May 2017 11:07:09 +0200 (CEST) Received: (qmail 63423 invoked by uid 500); 21 May 2017 09:07:07 -0000 Mailing-List: contact issues-help@ariatosca.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ariatosca.incubator.apache.org Delivered-To: mailing list issues@ariatosca.incubator.apache.org Received: (qmail 63414 invoked by uid 99); 21 May 2017 09:07:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 21 May 2017 09:07:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 44C80190D50 for ; Sun, 21 May 2017 09:07:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id T6FUIx13ifZO for ; Sun, 21 May 2017 09:07:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 02EC05F3A1 for ; Sun, 21 May 2017 09:07:06 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 5A92EE005B for ; Sun, 21 May 2017 09:07:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5E2672193C for ; Sun, 21 May 2017 09:07:04 +0000 (UTC) Date: Sun, 21 May 2017 09:07:04 +0000 (UTC) From: "Ran Ziv (JIRA)" To: issues@ariatosca.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ARIA-113) Custom log handlers in operations/workflows MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 21 May 2017 09:07:10 -0000 [ https://issues.apache.org/jira/browse/ARIA-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018766#comment-16018766 ] Ran Ziv commented on ARIA-113: ------------------------------ This issue has become irrelevant - rather than supporting custom log handlers, all logs are written to the storage, and so "alternative handlers" can simply read them from there. > Custom log handlers in operations/workflows > ------------------------------------------- > > Key: ARIA-113 > URL: https://issues.apache.org/jira/browse/ARIA-113 > Project: AriaTosca > Issue Type: Story > Reporter: Maxim Orlov > Priority: Minor > > Decide whether we want to support workflow/operation custom log handlers. If so, we could implement it using the {{with_handlers}} context manager. -- This message was sent by Atlassian JIRA (v6.3.15#6346)