Feature #6416
openAbility to remove an included puppet class from a nested host group and a host
Description
The ability to remove an inherited puppet classes from the included classes from both a nested host group and a host. Also the ability to re-add the removed classes to both host group and nodes
Suggestion:
When excluding an inherited class from either a host group or node still visibly show the class as greyed out with a click to add icon (+) beside them similar to when remove classes from host groups or nodes currently
Use Case:
You have multiple user account classes that you bind to every node via a host group, with a nested host groups for your stage and production environments. Also including even further nested host groups for specific node types (web, dns, ftp).
The user jim has made some mistake and is no long allowed to manage the dns nodes in your environment. You want to remove his account from those servers without restructuring your host groups or processes.
or
The users jim is waiting on approval to manage the production dns node2 server, so he is excluded from that specific node until approval is granted
-global_common ( HG) <classes: accounts::users::jim, accounts::users::bob, accounts::users::tim, accounts::users::scott> ----- These users could even be in a Config Group that is applied to the Host Group -stage -web -dns <- accounts::users::jim excluded from all nodes in this HG ~ node1 ~ node2 -ftp -production -web -dns ~ node1 ~ node2 <- accounts::users::jim excluded from this specific node -ftp
Updated by Steven Bambling over 10 years ago
Steven Bambling wrote:
The ability to remove an inherited puppet classes from the included classes from both a nested host group and a host. Also the ability to re-add the removed classes to both host group and nodes
Suggestion:
When excluding an inherited class from either a host group or node still visibly show the class as greyed out with a click to add icon (+) beside them similar to when remove classes from host groups or nodes currently
Use Case:
You have multiple user account classes that you bind to every node via a host group, with a nested host groups for your stage and production environments. Also including even further nested host groups for specific node types (web, dns, ftp).
The user jim has made some mistake and is no long allowed to manage the dns nodes in your environment. You want to remove his account from those servers without restructuring your host groups or processes.
or
The users jim is waiting on approval to manage the production dns node2 server, so he is excluded from that specific node until approval is granted
--global_common ( HG) <classes: accounts::users::jim, accounts::users::bob, accounts::users::tim, accounts::users::scott> ----- These users could even be in a Config Group that is applied to the Host Group
--stage
--web
--dns <- accounts::users::jim excluded from all nodes in this HG
~ node1
~ node2
--ftp
--production
--web
--dns
~ node1
~ node2 <- accounts::users::jim excluded from this specific node
--ftp
Updated by Dominic Cleal over 8 years ago
- Description updated (diff)
- Category set to Puppet integration
Updated by Dominic Cleal over 8 years ago
- Has duplicate Bug #16045: Nested hostgroup does not provide a option to override puppet classes coming from parent hostgroup added
Updated by Daniel Lobato Garcia over 8 years ago
- Target version changed from 1.7.1 to 117