[
https://issues.apache.org/jira/browse/BROOKLYN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399627#comment-15399627
]
ASF GitHub Bot commented on BROOKLYN-249:
-----------------------------------------
Github user aledsage commented on a diff in the pull request:
https://github.com/apache/brooklyn-server/pull/279#discussion_r72821487
--- Diff:
locations/jclouds/src/main/java/org/apache/brooklyn/location/jclouds/JcloudsLocation.java
---
@@ -527,7 +531,7 @@ public ComputeService getComputeService(Map<?,?> flags)
{
public ComputeService getComputeService(ConfigBag config) {
ComputeServiceRegistry registry =
getConfig(COMPUTE_SERVICE_REGISTRY);
- return
registry.findComputeService(ResolvingConfigBag.newInstanceExtending(getManagementContext(),
config), true);
--- End diff --
This was added to fix "BROOKLYN-249: JcloudsLocation resolves external
config" (see commit 99dd3ba4fc507988bdecd4e57c2b36cbb465b2a5)
> 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)
