Fixed issues (MySQL)

MYSQL-250

Plugin operation fails while writing logs if any previous logs exist in the toolkit directory.

If the original environment (operating system) user is replaced with a new user, connector operations will fail due to the existence of logs and the new user’s lack of file privileges. In this release, user permissions have been updated so that connector operations are completed successfully. 

MYSQL-275

The mysqldump failing because of special characters

The MySQL dump would fail if the password contained any of the following characters: $ ``! \.

MYSQL-292

Changes in my.cnf allowed properties - removing some restriction

Restrictions have been lifted to allow special characters and longer character lengths to support many MySQL runtime parameters specified during VDB provisioning.

MYSQL-298

Unable to refresh MySQL VDB due to shutdown timeout

The timeout length has been increased from 3 to 15 minutes so that shutdown timeout errors are avoided.

MYSQL-242

Plugin Operation fails while writing logs if any previous logs exist in the toolkit directory.

MYSQL-230

Added missing my.cnf update logic within the Rollback operation.

MYSQL-225

A quick fix to prevent code break.

MYSQL-214

Verified the CLI syntax, and conveyed it to the support team.
Validated major CLI operations for the MySQL Document revamp as well.

MYSQL-210

ESCL-4684 - Retry logic for Refresh

MYSQL-207

Runbash failing while shutting down(kill) the MySQL instance

MYSQL-118

The MySQL Instance name is changed to Source Config name to reduce confusion during configuration and standardize across our connectors.

MYSQL-138

The length of the MySQL Instance name has now been changed to support up to 255 characters.

MYSQL-81

Changed the command to change the root password which facilitates seamless working of the linking process.

MYSQL-72

Changed the commands to take backups as they were deprecated.