[ ] remove the local_id entry from default configuration output (either create a new config just for printing or add en exclusion parameter for printing MultiTreeMap)
[x] remove the id of the deployment from the context of all entities as it generates warnings
[ ] when in-context-of is used, the name remains in the list (although only the id is needed). Remove the name.
[ ] entities in the deployment must be referred to (e.g. in in-context-of) by their full name, including the kind. The kind should not be necessary
[ ] implement description of not-pre-defined categories
[ ] can we specify category properties in the XML?
[ ] introduce entities with required name / required kind
[ ] implement all properties also as attributes in the configuration
[ ] should an empty no-attributes agent tag be admissible? In what scenario?
[ ] -i for interactive console which allows adding (and removing) support / agents / other entities
[ ] -select to select the local node configuration in the deployment file (e.g. have the same deployment file for multiple nodes and just select different local nodes)
[ ] introduce tree control: <categ goes back to categ and << goes to root (above nodes)
[ ] between a category and its mandatory parent there may also be other categories (use case: agent arrays as entities that can be managed as a whole)
[ ] fuse trees from XML and CLI in the case of elements with optional parents
[ ] implement q attribute in XML that is parsed by the CLI parser
[ ] implement special categories such as
[ ] -all-of:always category par:val+ (copy/fuse the subordinate tree to all children of category)
[ ] -all-of:missing category par:val+ (insert the values in the subordinate tree in all children of category, but only if no such parameter is already defined).
local_id
entry from default configuration output (either create a new config just for printing or add en exclusion parameter for printing MultiTreeMap)in-context-of
is used, the name remains in the list (although only the id is needed). Remove the name.in-context-of
) by their full name, including the kind. The kind should not be necessary-i
for interactive console which allows adding (and removing) support / agents / other entities-select
to select the local node configuration in the deployment file (e.g. have the same deployment file for multiple nodes and just select different local nodes)<categ
goes back to categ and<<
goes to root (above nodes)q
attribute in XML that is parsed by the CLI parser-all-of:always category par:val+
(copy/fuse the subordinate tree to all children of category)-all-of:missing category par:val+
(insert the values in the subordinate tree in all children of category, but only if no such parameter is already defined).