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 1746C200C86 for ; Wed, 31 May 2017 10:56:31 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 15C28160BCB; Wed, 31 May 2017 08:56:31 +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 543BC160BBA for ; Wed, 31 May 2017 10:56:30 +0200 (CEST) Received: (qmail 27477 invoked by uid 500); 31 May 2017 08:56:29 -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 27465 invoked by uid 99); 31 May 2017 08:56:29 -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, 31 May 2017 08:56:29 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 325D9E03B3; Wed, 31 May 2017 08:56:29 +0000 (UTC) From: drigodwin To: dev@brooklyn.apache.org Reply-To: dev@brooklyn.apache.org References: In-Reply-To: Subject: [GitHub] brooklyn-server issue #712: Updated GCE features Content-Type: text/plain Message-Id: <20170531085629.325D9E03B3@git1-us-west.apache.org> Date: Wed, 31 May 2017 08:56:29 +0000 (UTC) archived-at: Wed, 31 May 2017 08:56:31 -0000 Github user drigodwin commented on the issue: https://github.com/apache/brooklyn-server/pull/712 I agree @andreaturli, we should use this when it becomes available. I think we should also make this change in the meantime however as this fixes GCE in the short term. --- 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. ---