Actions
Enhancement #21857
openWe should have a warning on impact of agent reset on root server
Pull Request:
UX impact:
I hate Rudder for that
Suggestion strength:
Want - This would make my life a lot easier but I can manage without
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Name check:
To do
Fix check:
To do
Regression:
No
Description
If ones does a rudder agent reset
on root server, it causes restauration of initial policies, which in turn means that default allowed networks will be restored.
On a big installation, especially if relay servers are present, it will cause a bit of disruption until a full regeneration is triggered.
So we need to at least add a warning, or perhaps force to have the user add a specific message as a command parameter to let him have a change to understand what it means (and especially in the context of lots of consoles open on nodes and servers, to let the user know that perhaps it is not doing what he thinks)
Example of expected interaction:
$ rudder agent reset You are on the root server. Executing `rudder agent reset` will cause initial policies to get restored. Among other things, it means that allowed netwoks will be reset to their default values and nodes won't be able to conect until a full policy regeneration is done. If you know what you are doing, please use `rudder agent reset --on-policy-server` (exit 1) $ rudder agent reset --on-policy-server
Or something like that (wording or parameter name can be improved)
Actions