Do a module caching on the agent side #58
Description
Is your enhancement related to a problem? Please describe.
Current module delivery process do not handle case when module can be removed from the policy/agent from a group/etc. while agent is disconnected, such a limitation do not allow to limit amount of "cleanups" being done by module cause currently every time module is being stopped (no matter what reason) it MUST do whole cleanup of it's work cause next time it is possible that agent would start and according to a policy this "deleted" module won't arrive on agent side at all.
Designs
The idea is to cache all modules on an agent side and on next start of the agent first spawn all modules from the cache, then do a connection to a server and handle "modules change" requests, this design will allow to guarantee that agent after restart as a first thing recover it's state and only then do a change.
Describe alternatives you've considered
It is possible also to do a cache on a server side and do kind of "start" of the agent from this cache and somehow wait till agent is fully set to it's previous state and only then handle new state changes, but such a design requires to cache a lot of things in one place and carefully manipulate this cache thing which looks much less trivial and also still leaves problem with delivering too much things on agent side every time agent is restarted.