Github user tbouron commented on a diff in the pull request:
https://github.com/apache/brooklyn-server/pull/358#discussion_r81125194
--- Diff:
rest/rest-resources/src/main/java/org/apache/brooklyn/rest/transform/EntityTransformer.java
---
@@ -162,7 +163,7 @@ public static EntityConfigSummary
entityConfigSummary(Entity entity, ConfigKey<?
SensorTransformer.addNamedAction(lb, na,
entity.getConfig(config), config, entity);
}
- return entityConfigSummary(config, label, priority, lb.build());
+ return entityConfigSummary(config, label, priority, false,
lb.build());
--- End diff --
Well, yes and no. I mean, the UI does not check a `pinned` flag for managed
entities but only for catalog templates. So technically, config will never be
invisible.
However, I do agree that the REST API shouldn't return a `pinned: false`
for this case for I'll update for a nullable field.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
