Github user ahgittin commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/484#issuecomment-72207047
@alasdairhodge RTFI (where I = issue). this addresses the real problem of
passwords being blatantly obvious to the person walking past your desk, where
you have entitlement and sometimes requirement to see the real information.
controlling people's entitlements to data is a totally separate problem for
which the entitlement subsystem can be used currently. a good addition to this
would be the ability to define sets of sensors where we might want to grant RO
or RW or NO access (where NO is not an acronym :) ). however i think a single
`@Hidden` annotation is too coarse as it assumes there is only ever one such
set.
while the distinction you draw between "you can know it exists but you
can't see the value" and "you can't even know it exists" is a valid one, is
there really any use case? i'd drop it, in favour of only the latter.
---
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.
---
