Containerized set metadata

[mvdbeek]

This is how it's enabled:

                "metadata_config": {
                    "containerize": True,
                    "engine": "docker",
                    "image": "galaxyproject/galaxy-job-execution",
                },

inside your environment (see integration test). The image is of course not published yet. docker build -f packages/job_execution/Dockerfile . -t galaxyproject/galaxy-job-execution to build the image if you want to play with something that is not the integration test.

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[mvdbeek]

lagom.exceptions.TypeOnlyAvailableAsAwaitable: <no detail available> is specific to python 3.8 and doesn't happen on 3.11 ... guess the EdamDictType type variable is at fault.

[bernt-matthias]

Would it be a good idea to document this, e.g. in the job_conf.sample.yml or docs. Maybe with usecases, ie when this should be used.

Guess this works only (and makes sense) in containerized job destinations?

[mvdbeek]

Sure, once this is working and we've agreed on the details.