We are trying to use migrate with a MySQL database hosted in Azure with Azure Database for MySQL and have hit an issue. Azure MySQL usernames contain an @ sign. Unfortunately this messes up migrate because the database connection is being parsed as a URL. I was on an older version and the @ sign was being escaped. I just pulled the latest version and see that this commit changed the order of when the mysql:// is removed so passwords aren't escaped. Unfortunately now I get an error parsing the url "first path segment in URL cannot contain colon". A sample connection string looks like mysql://someuser@samplehost:password@tcp(samplehost.mysql.database.azure.com:3306)/SampleDB?tls=skip-verify&allowNativePasswords=true

Any ideas how to work around this?