The modules install command should be designed similarly to the simple install command. Execution of the command should result in downloading the required module from the "customer zone", the latest version or given the version specified in the command, and suitable for the current operating system and its architecture.
The archive with the module is then extracted into the "modules" folder that was specified first in the tt.yaml file.
Unlike the search command, the name of the module to be installed must be specified in full (masks are not allowed). For example: tt modules install aeon 0.1 - install aeon module of the last available patch version in the 0.1 set. Without specifying the version, the module of the latest available version will be installed.
Task is blocked until will be done:
1009 - Here should be used code to handle modules in the "customer zone".
The
modules installcommand should be designed similarly to the simpleinstallcommand. Execution of the command should result in downloading the required module from the "customer zone", the latest version or given the version specified in the command, and suitable for the current operating system and its architecture.The archive with the module is then extracted into the "modules" folder that was specified first in the
tt.yamlfile.Unlike the
searchcommand, the name of the module to be installed must be specified in full (masks are not allowed). For example:tt modules install aeon 0.1- installaeonmodule of the last available patch version in the0.1set. Without specifying the version, the module of the latest available version will be installed.Task is blocked until will be done:
1009 - Here should be used code to handle modules in the "customer zone".
1012 - Here required to use modified the
tt.yaml