Idea ID: 1795684

Back-office config change warnings

Status : Waiting for Votes
Waiting for Votes
See status update history
over 2 years ago


My idea is like title says, we need some better warnings for back-office config changes.

(BO -> configurations -> security /email / ldapcms...)

Today when someone makes a change to these configs, it just lets anyone hit save and then automatically restarts the pods. These seemingly basic changes can cause the whole system to go down for 20 minutes + while all the pods restart in the correct order.

It would be nice to see a final warning before hitting save, something like "these pods will be restarted if config is changed.. are you sure??"

or maybe a scheduler here so we could schedule these changes for later?


I realize these configurations aren't being changed a lot but a warning would be nice or at least copy this document: to the other versions of smax.



Parents Comment Children
No Data