Add a nice way to deploy scripts

[corentincarton]

Is your feature request related to a problem? Please describe.

We should add a shortcut to deploy shell/bash scripts and python scripts. Maybe through an entry in the tools?

tools:
  scripts:
     myscript:
       type: shell
       retrieve:
         type: git
         source: ...

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

Organisation

No response

[oiffrig]

That would be nice indeed. On my side, I use this to deploy some python scripts:

tools:
  packages:
    py_scripts:
      type: copy
      source: "{PWD}/scripts"
      files:
        - foo.py
        - bar.py
      post_script: |
        mkdir -p $LIB_DIR/$ENV_NAME/scripts
        cp * $LIB_DIR/$ENV_NAME/scripts

[corentincarton]

Thanks @oiffrig for this example! This is also how I would do.
The issue here is that a python or shell script probably never comes alone, it will always depend on some kind of environment (venv, conda, module, etc.) and I'm not sure what would be the best way for users to do this. Shall we have a script entry in the tools, that then depends on an environment? But do we specify the scripts sources in the script section? Or do we link them with a package, which will be installed as in your example?

[oiffrig]

The way I use the package in my example above is by adding it to an environment:

  environments:
    suite_env:
      type: system_venv
      depends: [python, toolbox]
      packages: [py_scripts]

I've also played with a similar setup where the environment is just a folder, which works well for e.g. shell scripts that don't have specific dependencies.

Alternatively, we could use the dependency system as well to make it consistent with the rest of the tools. But then how would you describe the deployment? You would anyway need to specify a location somehow, having it installed into an environment makes this clear.