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 3C5C0200CA4 for ; Wed, 7 Jun 2017 11:11:13 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3AF93160BD0; Wed, 7 Jun 2017 09:11:13 +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 779A7160BB6 for ; Wed, 7 Jun 2017 11:11:12 +0200 (CEST) Received: (qmail 79072 invoked by uid 500); 7 Jun 2017 09:11:10 -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 79061 invoked by uid 99); 7 Jun 2017 09:11:10 -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; Wed, 07 Jun 2017 09:11:10 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 23FA8DFBDA; Wed, 7 Jun 2017 09:11:10 +0000 (UTC) From: andreaturli To: dev@brooklyn.apache.org Reply-To: dev@brooklyn.apache.org References: In-Reply-To: Subject: [GitHub] brooklyn-docs issue #194: Feature/effectors Content-Type: text/plain Message-Id: <20170607091110.23FA8DFBDA@git1-us-west.apache.org> Date: Wed, 7 Jun 2017 09:11:10 +0000 (UTC) archived-at: Wed, 07 Jun 2017 09:11:13 -0000 Github user andreaturli commented on the issue: https://github.com/apache/brooklyn-docs/pull/194 thanks @murdoaird, I think the first paragraph is an attempt to do that. SSH and HTTP Effectors are really generic and (hopefully) flexible so it is not easy to explain why you might use them. I'd appreciate some hints or maybe we can close this PR and improve it later on with a subsequent PR? --- 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. ---