Github user aledsage commented on the issue:
https://github.com/apache/brooklyn-server/pull/612
@bostko (cc @tbouron) Thinking about this more, I'm not sure what types we
should support for tags. Maybe accepting any object is a bad idea, as it might
make subsequent features harder to support (e.g. support for looking up /
processing tags).
On the other hand, locking down the types to be just strings without a good
reason seems too extreme.
Looking at the REST api
(`org.apache.brooklyn.rest.resources.EntityResource.listTags()`), it turns the
tags into json via the standard mechanism. It can therefore handle non-string
types. if you use something that does not have a good json representation, then
it becomes a lot less useful. But arguably that's the user's problem
(presumably they had a reason for putting the object in the tags in the first
place).
---
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.
---
