Thanks for making this snap. Nice idea!

Have you considered using the "tracks" functionality to enable multiple different versions of the same snap to be published?

That way, someone could stay on the 8.0 LTS release of MySQL or opt for the newer 8.2 or 8.3 releases.

This could be achieved with separate branches on the git repo and GitHub actions to do the build and push to the store. The snapcrafters repo has some examples of this, like (most recently) the sublime-text snap, which has a "dev" track as well as the "latest" one.

I need the ability to automate the installation and setup of MySQL as part of a custom Ubuntu Core build. Would it be possible to incorporate some kind of switch to either leave the root password unset or have the ability to set it to a known value?

In my workflow I want to install the MySQL snap and then install my custom app snap which performs a database migration in the post-refresh hook. Since retrieving the password is a manual step this means the installation can't be automated.

For now I am going to create my own version of this snap using the --initialize-insecure flag. I'm happy to contribute if it helps but I'm not sure I understand snaps enough at this stage.

this is the error i get when it try to source a .sql file

mysql> source /home/<username>/Downloads/companydb.sql;
ERROR: 
Failed to open file '/home/<username>/Downloads/companydb.sql', error: 13

i tried to find the solution but cant seem to find any