You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Aled Sage (JIRA)" <ji...@apache.org> on 2016/04/06 18:20:25 UTC

[jira] [Resolved] (BROOKLYN-249) errors using external config for JcloudsLocation

     [ https://issues.apache.org/jira/browse/BROOKLYN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aled Sage resolved BROOKLYN-249.
--------------------------------
       Resolution: Fixed
         Assignee: Aled Sage
    Fix Version/s: 0.9.0

> errors using external config for JcloudsLocation
> ------------------------------------------------
>
>                 Key: BROOKLYN-249
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-249
>             Project: Brooklyn
>          Issue Type: Bug
>            Reporter: Aled Sage
>            Assignee: Aled Sage
>             Fix For: 0.9.0
>
>
> Using 0.10.0-SNAPSHOT (also affecting 0.9.0-rc2), I hit problems using external config with JcloudsLocation.
> First it failed to resolve the external config for the ssh publicKeyData and privateKeyData.
> After fixing that, it failed to rebind to my persisted state that included the external config in the location (it tried to coerce the {{DeferredSupplier}} to a String).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)