Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
Date: Wed, 19 Apr 2017 10:42:42 +0000 (UTC)
From: "Aled Sage (JIRA)" <jira@apache.org>
To: dev@brooklyn.apache.org
Message-ID: <JIRA.13065051.1492598525000.316514.1492598562134@Atlassian.JIRA>
In-Reply-To: <JIRA.13065051.1492598525000@Atlassian.JIRA>
References: <JIRA.13065051.1492598525000@Atlassian.JIRA> <JIRA.13065051.1492598525690@jira-lw-us.apache.org>
Subject: [jira] [Created] (BROOKLYN-476) Externalized config fails for BYON
 location with windows machines
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 19 Apr 2017 10:42:48 -0000

Aled Sage created BROOKLYN-476:
----------------------------------

             Summary: Externalized config fails for BYON location with windows machines
                 Key: BROOKLYN-476
                 URL: https://issues.apache.org/jira/browse/BROOKLYN-476
             Project: Brooklyn
          Issue Type: Bug
    Affects Versions: 0.10.0
            Reporter: Aled Sage
             Fix For: 0.11.0


A customer wants to use externalized-configuration for a BYON location with windows VMs. Unfortunately this does not work (but does for ssh-based VMs).

Below is a simple example. The first snippet is for the {{brooklyn.cfg}} file; the second is the blueprint that references it:

{noformat}
brooklyn.external.credentials=org.apache.brooklyn.core.config.external.InPlaceExternalConfigSupplier
brooklyn.external.credentials.byonPassword=pa55wOrd
{noformat}

{noformat}
  byon:
    hosts:
    - winrm: 192.168.1.2
      user: admin
      password: $brooklyn:external("credentials", "byonPassword")
      osFamily: windows
services:
- type: org.apache.brooklyn.entity.software.base.VanillaWindowsProcess
  brooklyn.config:
    launch.command: echo launch
    checkRunning.command: echo running
{noformat}


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)