Tim Gross
Tim Gross
> As true as this is, many 3rd party projects that stacks rely on don't tag their containers properly, and it is a large maintenance burden to set up your...
> Couldn't the driver have an option to blindly pull and replace containers on a timer? It would be better than nothing and still offer eventual consistency for certain use...
Alternately, now that we'll have Variables in Nomad 1.4.0, we could let users get secrets from there.
Note for implementation: one of the things we deliberately did with [Task Access to Variables](https://www.nomadproject.io/docs/concepts/variables#task-access-to-variables) was to prefix the task variables path with `nomad/jobs`, leaving room for us to do...
We update issues when they're being worked on. So no news.
See also https://github.com/hashicorp/nomad/issues/7290
Resurrecting this issue a bit with a unit test inspired by a test case provided by @maksimnosal ```go func TestServiceScheduler_ComputedClassReporting(t *testing.T) { h := tests.NewHarness(t) node0 := mock.Node() node0.Attributes["attr.unique.hostname"] =...