Rudder

Sometimes one logical change requires multiple modifications on directives / rules / groups.

Example:
I want to roll out a MOTD Config for a new set of servers. I have to:

1. Create a group for a new rule -> CR#1 => Why is creating a group a CR? This did not influence any of the existing rules...
2. Create a Directive from a Technique, that does something (no CR created yet)
3. Create a Rule and add Directive and Group to it, then save -> CR#2

These steps belong to one logical action.

Additionally, if I am in the need for example to create a new default setting for a new PostgreSQL-Server, I might need to change about 3-4 settings in different groups/directives/rules, and it still is one tightly coupled action, that needs to be rolled (or declined) together, so I'd need to "start recording", to my stuff, then submit for a change request.

Example for this could be the LuCI interface from OpenWRT, where you can click together your config as you wish, then review all your changes, and commit it to NVRAM (which would be the approval + rollout step in our case).