Hi Alex, On 23 January 2018 at 10:39, Alex Heneveld <[email protected]> wrote:
> What values does it need? Would it make sense to put it into > BasicMachineMetadata and adjust JcloudsLocation.getMachineMetadata to add > it for everything? > That would be a good solution for the medium or long term - there's not much reason for having all the `NodeMetadata`, cherry-picking out the IP address and then throwing the rest away! I suppose it's theoretically possible that the metadata might include some sensitive information that is not appropriate to be exposed in some kinds of service provider use cases but I think that's unlikely to be a general problem. What I specifically need is the `userMetadata`. The particular cloud provider in question sets additional metadata k/v pairs, and one of these values I would like to expose in the GUI. However I'm really looking for a way to do this in the short term (without waiting for a release cycle). The other option if you want to opt-in at an initializer is for it to do > `location.getConfig(CALLER_CONTEXT)` -- there isn't guaranteed to be > exactly one Entity for each Location > (might have multiple, might have none) so there isn't a > `Location.getEntity()` and this value might not be an `Entity`, but if > there _is_ such a one-to-one releationship where an entity creates a > location, the usual pattern is that the Entity will set itself as this > context. > Thanks, I'll look into this. Cheers Richard.
