1.12.58: the broker should pass the archetype to the object template

[jouvin]

Currently, the plenary object template generated by the broker doesn't contain anything about the Aquilon archetype used to build the host. This makes impossible for a generic (not archetype-based, e.g. feature or OS templates in the template library) template to include an archetype-specific configuration with something like:

include format('site/%s/feature_config', ARCHETYPE);

It would be good to have the broker adding this information in the generated template, either by defining a (final) variable ARCHETYPE or by adding it to the profile configuration as part of the host data. One advantage for using a variable is that it would be possible to define it before the initial LOADPATH with the following construct that will make the things more readable and avoid any risk of divergence:

final variable ARCHETYPE = 'linux';
variable LOADPATH = list(ARCHETYPE);

This issue is a spin off of the very long #86 discussion...

[jrha]

I would actually be very happy if it just did:

"/system/archetype/name" = "foo";

Our usage of the ARCHETYPE variable is largely legacy and could be easily replaced with value("/system/archetype/name").

[jrha]

In fact, I just checked and we no longer make use of ARCHETYPE, everything has already switched over.

[jouvin]

I'm also happy if the broker assign the config path rather than a variable but I'd suggest my construct to make clear that loadpath is initialized with it