Project

General

Profile

Actions
Copy link

User story #3824

closed

dependencies between directives

Added by Fabrice FLORE-THÉBAULT over 11 years ago. Updated almost 7 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
4.1.10
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

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).

Actions
Copy link
 #1

Updated by Vincent MEMBRÉ over 11 years ago

  • Assignee set to Jonathan CLARKE
  • Target version set to Ideas (not version specific)

This is an interesting feedback, It's not convenient to organize and apply a complex Configuration now (too many directives to create, too many clicks, and finally link all Directives to a Rule ...), and we should definitely improve that process.

As said in other issues you openened, We will change Directive/Technique in 2.8, and we should look into improving this part of rudder too.

Actions
Copy link
 #2

Updated by Jonathan CLARKE over 11 years ago

  • Assignee changed from Jonathan CLARKE to François ARMAND
  • Target version changed from Ideas (not version specific) to 2.8.0~beta1

This is a good idea. I like the approach you describe and the concept of creating reusable "sets" of directives.

Let's see how this could work given the changes in 2.8.

Actions
Copy link
 #3

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.8.0~beta1 to Ideas (not version specific)

This is not planned in the Rudder 2.8 roadmap

Actions
Copy link
 #4

Updated by Dennis Cabooter almost 11 years ago

I like this idea a lot too. :)

Actions
Copy link
 #5

Updated by François ARMAND almost 7 years ago

  • Status changed from New to Rejected
  • Assignee deleted (François ARMAND)
  • Target version changed from Ideas (not version specific) to 4.1.10

I think that technique built from the technique editor exactly fullfill that need.
I'm closing that one, but please reopen if the use case is different.

Actions
Copy link

Also available in: Atom PDF