MSB-265: Introduce upgrade list and db backup before upgrade

[abdulazizali77]

No description provided.

[abdulazizali77]

@vetss Sergey please have a look
-I have not added the new DB options to shell executor as i think it shouldnt be modifiable during runtime. What do you think?
-Do you think we should populate the dbLogin dbPass in UssdProperties.xml or should we fetch it from the *-ds.xml? (not sure how to do that yet)

[vetss]

Hello @abdulazizali77

I checked your PR. Comments:

• no manaual / CLI / GUI updates (let us do it further when all other staff became working)
• when adding of new filelds into xml config files we may not add them into the end of the file (config files from old versions will not be loadable, this is an xml lib usage issue). So we need to add into a middle of the file
• have you tested your code locally ? I mean prepare some database structure and run a server and check how will it make backups or database structure updates ? I have some doubts for example for module "checkUpgradePath()" does not push value "src" back to upper level.
• you use a specific mysql staff. Let's test what will happen in case of another database, may be it will bring us some malfunctions. Ideally if we manage to reuse of staff that if universal for any database. For example "SELECT TABLE_NAME FROM INFORMATION_SCHEMA.COLUMNS" may be replaced by a "select from ***" and try to catch an Exception. All of this demands carefuly testing. You may add a unit test by the way.

I have not added the new DB options to shell executor as i think it shouldnt be modifiable during runtime. What do you think?

Such options may be modifyable during runtime for usage in the next start. We need to mention it in the manual.

Do you think we should populate the dbLogin dbPass in UssdProperties.xml or should we fetch it from the *-ds.xml? (not sure how to do that yet)

Login and pass - we can include it into an xml file. "*-ds.xml" is also an option but it may take efforts, not sure this is really needed.