Details
Description
Currently there is no way for a module to track client specific options that affect all services for that client and module (or module row). The primary benefit of which is to store client specific information for a set of services. For example, Plesk, SolusVM, and other modules require creating a single client account for multiple services.
This tasks adds a new module_client_meta table to hold this data.
client_id, module_id, module_row_id (0/optional), key, value, serialized, encrypted
This task also adds a ModuleClientMeta model class that allows modules to read/write options for this data store.