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 AC3EA200C30 for ; Tue, 7 Mar 2017 18:01:08 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id AAC5A160B68; Tue, 7 Mar 2017 17:01:08 +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 E7751160B65 for ; Tue, 7 Mar 2017 18:01:07 +0100 (CET) Received: (qmail 4822 invoked by uid 500); 7 Mar 2017 17:01:07 -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 4801 invoked by uid 99); 7 Mar 2017 17:01:06 -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; Tue, 07 Mar 2017 17:01:06 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id BA62CDFD9E; Tue, 7 Mar 2017 17:01:06 +0000 (UTC) From: drigodwin To: dev@brooklyn.apache.org Reply-To: dev@brooklyn.apache.org References: In-Reply-To: Subject: [GitHub] brooklyn-docs issue #152: Docs for SharedLocationSecurityGroupCustomizer Content-Type: text/plain Message-Id: <20170307170106.BA62CDFD9E@git1-us-west.apache.org> Date: Tue, 7 Mar 2017 17:01:06 +0000 (UTC) archived-at: Tue, 07 Mar 2017 17:01:08 -0000 Github user drigodwin commented on the issue: https://github.com/apache/brooklyn-docs/pull/152 Thanks @iyovcheva, I think it would be worth specifying that this only works on some clouds and perhaps listing the clouds. --- 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. ---