Is there any intention to add a function in the template (or maybe it exists and I have missed it) to allow the orchestrator to query the api from within the HOT document? We anticipate having some very large and complex ecommerce environments. Managing all that from a single HOT document may get a little unwieldy.

When working within the template it is easy enough to reference things you need for the various resource services using get_resource: the_resource. If I have two templates, let's say one is for the full size web experience and the other manages the mobile part of my application, and I need to cross reference between the two for shared resources then I have to resort to knowing the uuid's for those resources if they did not originate in my template. I can't reference them by an easily remembered name. I understand the reason for this is that the resource-name namespace is not guaranteed to be unique (unless, maybe, at the stack level?). Yet in very large projects it would be very nice to be able to reference resources created outside the template by a name rather than a uuid.

Maybe this exists and I've just overlooked it (wouldn't be the 10th time :-) ). It would be nice to have something like:

get_resource: {namespace}:resource-name

We've considered creating some sort of pre-compiler for the HOT doc to do something like this and enforce the namespace ourselves.