You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The runner should take a HCL template and populate it with the job specifics. This way the template can be swapped out with the deployment and every possible parameter for running a job on Nomad doesn't need to be forwarded via the Galaxy config.
The text was updated successfully, but these errors were encountered:
The k8s and docker runners need to be rewritten to accept templates as well.
For k8s, it should take a k8s YAML file, and for docker it should take a docker compose YAML file.
For k8s, pykube needs to be replaced with https://github.com/kubernetes-client/python
For docker, compose functionality can be directly imported from https://github.com/docker/compose
All YAML files should be passed through a templating engine first. Because YAML uses # as comments, it would be ideal to use Galaxies existing Cheetah template engine as Cheetah uses # to demark template directives.
https://pypi.org/project/python-nomad/
https://github.com/hashicorp/levant - relevant but not directly useable
The runner should take a HCL template and populate it with the job specifics. This way the template can be swapped out with the deployment and every possible parameter for running a job on Nomad doesn't need to be forwarded via the Galaxy config.
The text was updated successfully, but these errors were encountered: