Not all actions should require a VM restart

Hi Team :) This is mostly for VMs but also applicable to containers.

So a lot of actions require a restart in cycle, and some things of course needs an OS reboot to go into affect, like changing CPU, MEM and other hardware options.

But quite a few do not, like expanding an external disk or updating a server deployment tag. and it would be nice to avoid having to schedule maintenance windows for updating simple things, or simply a warning that changes will happen on next reboot would also be good, so my request is to only restart/warn when changing something that requires it, and this avoids the hard restart as well for a lot of things.

I understand this is a bigger ask, and I do not know the implication under the hood, as well as adding both UI and determining if a features requires it, but I think it could provide a lot of value especially to VMs that often do not run something in HA mode, but can't be restarted on a whim like a database.