Thank you, @nahsi! This looks like exactly what I need. No idea how I managed to overlook the fileset function while looking at file.
If I see it correctly, this would also restart the job each time one of the config files failed, because file is still used and that copies the contents into the Nomad job file?
Because that’s another problem I’ve had with my current artifact stanza/S3 setup: When I change a config file, Nomad doesn’t see any reason to restart a task, because it doesn’t redownload the artifacts from S3. I’ve been working around that with nomad alloc stop.