Rudder

To create complex tasks, dependencies between directives would be great.

It would be much more convenient than putting the glue in the rules.

Example:

I want to install the complete configuration for zabbix-agent on a node.

I have a specific configuration for the node class (mysql server for example), and a generic corporate configuration.

The specific configuration depends on the generic corporate configuration for zabbix-agent.

These configurations should be set up on hosts where zabbix-agent is installed: the directive "configuration for zabbix-agent" depends on the directive "deb package zabbix-agent" OR "rpm package for zabbix-agent".

Each of these packages depends on the presence of the zabbix repository on the node.

The zabbix repository depends on the importation of the zabbix repository key.

With dependencies between directives, you will have a rule asking for "configuration for zabbix-agent on mysql-server", and the dependencies between directives will do the rest.

For now, you have to resolve dependencies manually in the rule (in each rule, or create a generic rule with the dependencies and a specific rule).