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 DF6FC200AF6 for ; Sat, 11 Jun 2016 15:39:33 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DDFC4160A34; Sat, 11 Jun 2016 13:39:33 +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 28B6A160A2B for ; Sat, 11 Jun 2016 15:39:33 +0200 (CEST) Received: (qmail 66294 invoked by uid 500); 11 Jun 2016 13:39:32 -0000 Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@brooklyn.apache.org Delivered-To: mailing list dev@brooklyn.apache.org Received: (qmail 66283 invoked by uid 99); 11 Jun 2016 13:39:32 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Jun 2016 13:39:32 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id E5A11DFC4F; Sat, 11 Jun 2016 13:39:31 +0000 (UTC) From: aledsage To: dev@brooklyn.apache.org Reply-To: dev@brooklyn.apache.org References: In-Reply-To: Subject: [GitHub] brooklyn-server issue #195: Sanitize effector parameters when reporting an e... Content-Type: text/plain Message-Id: <20160611133931.E5A11DFC4F@git1-us-west.apache.org> Date: Sat, 11 Jun 2016 13:39:31 +0000 (UTC) archived-at: Sat, 11 Jun 2016 13:39:34 -0000 Github user aledsage commented on the issue: https://github.com/apache/brooklyn-server/pull/195 Whoever merges this, please look at marking https://issues.apache.org/jira/browse/BROOKLYN-282 as resolved. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---