Avoid logging MySQL connection configs

[meiji163]

Avoid logging MySQL connection configs.
Fix for https://github.com/github/gh-ost/security/code-scanning/2

PR Overview

This pull request addresses a code scanning alert related to clear-text logging of sensitive MySQL connection configurations by removing sensitive data from the error message.

• Introduces a new error constant, ErrMigrationNotAllowedOnMaster, which avoids logging sensitive connection configuration details.
• Refactors error handling to utilize the new constant instead of formatting sensitive configuration data into the error message.

Reviewed Changes

File	Description
go/logic/migrator.go	Defines a new error constant and updates existing error handling to prevent sensitive info logging

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

go/logic/migrator.go:27

• [nitpick] Consider rephrasing the error message for clarity by using past tense (e.g., 'attempted' instead of 'attempt') to improve grammatical accuracy.

ErrMigrationNotAllowedOnMaster = errors.New("It seems like this migration attempt to run directly on master. Preferably it would be executed on a replica (this reduces load from the master). To proceed please provide --allow-on-master.")

Tip: Copilot code review supports C#, Go, Java, JavaScript, Markdown, Python, Ruby and TypeScript, with more languages coming soon. Learn more