Nomad is an easy-to-use, flexible, and performant workload orchestrator that can deploy a mix of microservice, batch, containerized, and non-containerized applications. Nomad is easy to operate and scale and has native Consul and Vault integrations.
Similar to update stanza in #2806 - it would be nice if an env{) stanza could be put in
job -> env
job -> group -> env
job -> group -> task -> env
When an allocation is created the final env will be the result of:
job -> env
merged with job -> group -> env
merged with job -> group -> task -> env
The most specific env (closer to the task) will always "win" in the merge.
job "example" {
env {
FOO = "bar"
BAR = "baz"
BAZ = "qux"
}
group "sample" {
env {
FOO = "groupBar"
BAR = "groupBaz"
}
task "demo1" {
env {
FOO = "taskBar"
# FOO will be taskBAR
# BAR will be groupBaz
# BAZ will be qux
}
}
task "demo2" {
env {
# FOO will be groupBar
# BAR will be groupBaz
# BAZ will be qux
}
}
}
}
This would be really nice. I'm currently running the same binary with many shared environment variables, and there is no pretty way of organizing this at the moment.
Similar to
update
stanza in #2806 - it would be nice if an env{) stanza could be put injob -> env
job -> group -> env
job -> group -> task -> env
When an allocation is created the final env will be the result of:
job -> env
job -> group -> env
job -> group -> task -> env
The most specific env (closer to the task) will always "win" in the merge.
Similar would be great for
template{}