I suspect there are good reasons this isn't done now (technical and/or non-technical), but just in case this request is for a download feature.
For example I imagine executing dbdeployer download 8.0.11 (or somesuch) that'd use common defaults (e.g., 64-bit, generic glibc 2.12, ...) to download 8.0.11. It could become more complicated in the future.
On Linux it'd probably download this:
https://dev.mysql.com/get/Downloads/MySQL-8.0/mysql-8.0.11-linux-glibc2.12-x86_64.tar.gz
On macOS:
https://dev.mysql.com/get/Downloads/MySQL-8.0/mysql-8.0.11-macos10.13-x86_64.dmg
But that brings us to our first (and main) issue; how does it know the path? For example, might it ever be 8.0.11-1 instead of 8.0.11? Or 10.15 instead of 10.13? What about RC releases? Good questions and there are many more :)
Thankfully this functionality is a nice-to-have (not critical) so unexpected changes can cause failure without too much pain. But, download paths can (for the most part) be predicted. Not yet sure if other commands should use it (e.g., whether dbdeployer deploy single 8.0.11 might prompt I could not find v8.0.11; shall I attempt to download it?) Maybe.
Before I (or anyone) does further research, I'm curious if you see this as a possibility. If so then I'll dig a little deeper.
I suspect there are good reasons this isn't done now (technical and/or non-technical), but just in case this request is for a download feature.
For example I imagine executing
dbdeployer download 8.0.11(or somesuch) that'd use common defaults (e.g., 64-bit, generic glibc 2.12, ...) to download 8.0.11. It could become more complicated in the future.On Linux it'd probably download this:
https://dev.mysql.com/get/Downloads/MySQL-8.0/mysql-8.0.11-linux-glibc2.12-x86_64.tar.gz
On macOS:
https://dev.mysql.com/get/Downloads/MySQL-8.0/mysql-8.0.11-macos10.13-x86_64.dmg
But that brings us to our first (and main) issue; how does it know the path? For example, might it ever be 8.0.11-1 instead of 8.0.11? Or 10.15 instead of 10.13? What about RC releases? Good questions and there are many more :)
Thankfully this functionality is a nice-to-have (not critical) so unexpected changes can cause failure without too much pain. But, download paths can (for the most part) be predicted. Not yet sure if other commands should use it (e.g., whether
dbdeployer deploy single 8.0.11might promptI could not find v8.0.11; shall I attempt to download it?) Maybe.Before I (or anyone) does further research, I'm curious if you see this as a possibility. If so then I'll dig a little deeper.