🤔 The current problem
Currently the commands which do role inheritance break or reset may have a significant impact on the user defined architecture. Reseting role inheritance on an item which had a lot of unique permissions added (groups/ users as role assignments) means all of that will be lost the moment the inheritance is reset. In SharePoint this kind of operations need to be confirmed by the user. as @milanholemans pointed out we should also reproduce this behavior in CLI.
🎯 Aim
The aim would be to add a prompt before reseting or breaking the role inheritance on any level (web, list, listItem (file, folder)). Similar to what we have in all remove commands. Along the way we should add --confirm option to allow to the user to run the command without a prompt.
📃List of commands we should update
The following commands should be updated:
🚀 Target Release
v6
🔗 Originally mentioned
#3593
🤔 The current problem
Currently the commands which do role inheritance break or reset may have a significant impact on the user defined architecture. Reseting role inheritance on an item which had a lot of unique permissions added (groups/ users as role assignments) means all of that will be lost the moment the inheritance is reset. In SharePoint this kind of operations need to be confirmed by the user. as @milanholemans pointed out we should also reproduce this behavior in CLI.
🎯 Aim
The aim would be to add a prompt before
reseting orbreaking the role inheritance on any level (web, list, listItem (file, folder)). Similar to what we have in allremovecommands. Along the way we should add--confirmoption to allow to the user to run the command without a prompt.📃List of commands we should update
The following commands should be updated:
🚀 Target Release
v6
🔗 Originally mentioned
#3593