Hello,
I see that there now is an On/Off button in advanced configuration for dangerous upgrade, and several mentions already about using it in specific cases. Cool. I assume this means that the package is now part of the standard firmware.
If you need it, you click the button and turn it on to do what you need to do. OK. Can you also then turn it off to put the safety checks back on? Or does it have to remain on like leaving the package installed on the previous versions?
Also ... a bit more involved question, just a bit deeper. If I have a node with 3.22.12.0 that I want to update, and I use the dangerous upgrade package on it so I can update to 3.23.12.0 ... once I get updated can I then use this ON/OFF button and turn the dangerous update OFF ... putting safety protocols back in place?
Ed
I see that there now is an On/Off button in advanced configuration for dangerous upgrade, and several mentions already about using it in specific cases. Cool. I assume this means that the package is now part of the standard firmware.
If you need it, you click the button and turn it on to do what you need to do. OK. Can you also then turn it off to put the safety checks back on? Or does it have to remain on like leaving the package installed on the previous versions?
Also ... a bit more involved question, just a bit deeper. If I have a node with 3.22.12.0 that I want to update, and I use the dangerous upgrade package on it so I can update to 3.23.12.0 ... once I get updated can I then use this ON/OFF button and turn the dangerous update OFF ... putting safety protocols back in place?
Ed
