When using node_manager to manage a node_group; users lose the ability to pin nodes and modify rules via the PE console. This is inconvenient for users who wish to use node_manager to create node groups; however still require the flexibility to pin nodes and customise rules via the PE console.
This PR introduces the following behavior changes to the node_manager module.
When purge_behavior is set to "all", "data", "classes" or unset. There is no change to the behavior of this module.
When purge_behavior is set to "rule" or "none" node manager will.
Ensure rules set in the node_group code are enforced on the node group, while merging any existing rules and pinned nodes on the node group.
In the case of conflict between "Nodes must match all rules." and "Nodes may match any rule.". What is set in the PE console takes priority
Currently node_manager provides the ability to accept additional classes and data from users within the PE console by setting the purge_behavior parameter on a node_group basis. I would like to extend the module to include the ability to customise rules and pin nodes on a per node_group basis.
When using node_manager to manage a node_group; users lose the ability to pin nodes and modify rules via the PE console. This is inconvenient for users who wish to use node_manager to create node groups; however still require the flexibility to pin nodes and customise rules via the PE console.
This PR introduces the following behavior changes to the node_manager module.
When purge_behavior is set to "all", "data", "classes" or unset. There is no change to the behavior of this module. When purge_behavior is set to "rule" or "none" node manager will.
Currently node_manager provides the ability to accept additional classes and data from users within the PE console by setting the purge_behavior parameter on a node_group basis. I would like to extend the module to include the ability to customise rules and pin nodes on a per node_group basis.