Organizing complex jobs for nomad

[kinnalru]

We have complex system with 20 services (images). Most of them must share common variables like SYSTEM_INSTANCE and SYSTEM_PREFIX, so they must be passed to each task within environment.

I look for some way to organize such specification. How to share this varaible between ~20 jobs and ~2 groups in each job?

[lgfa29]

Hi @kinnalru

I think I answered a question similar to this a few minutes ago.

Nomad Job Spec Environment Variable Best Practices

Hi @nickpoulos I’m sorry to hear your team is having trouble migrating to Nomad. We appreciate you reaching out for help, and please keep raising these so we can help you and improve Nomad. You certainly don’t have to manually read keys into env vars if their name match the desired variable result. You can instead range over the result of the ls function and set each key as an environment variable with the specific value. Here’s an example based on what you provided: job "env" { dat…

Is this what you are looking for?

[kinnalru]

Nope
We decided to use ansible to preprocess our jobs definitions, so we have something like this:

 ...
    env {
      {{ macros.include('_env.nomad.j2') | indent(6) }}

      SYSTEM_INSTANCE = "{{ instance }}"
      SYSTEM_PREFIX = "start_{{ prefix }}.sh"
    }

    config {
      image = "{{ image }}"
      force_pull = true
    }
...