Tim Gross

@mvegter are you ready for a re-review on this? I didn't want to jump the gun if you were still in progress.

Hi @optiz0r! That's a real pain for sure. I don't have a good workaround for you. I've marked this for roadmapping. (Internal ref https://hashicorp.atlassian.net/browse/NMD-1021)

> BTW: body parsing would be intentional by operator and not enabled by default Under the Nomad [security model](https://developer.hashicorp.com/nomad/docs/architecture/security#personas) there are typically at least two personas at play here: the...

@gregory112 `deployments` that are complete won't ever get run again. Depending on your specific circumstance the `nomad alloc stop` command may be able to help you out here by forcing...

@lattwood as it turns out we were just talking about that internally and we definitely want to put together a doc that brings together all of deployments, `reschedule`, `restart`, and...

> Is this PR still relevant? This is still relevant because we have references to old versions floating around, but this PR as-is had some problems where we were removing...

Hi @EtienneBruines! I just want to make sure I understand the scenario and goal here. In the `leave_on_interrupt` case today, the reason why it's expected to be permanent is because...

> But I don't know whether it just always reports `Alive` whenever it's in the memberlist? The possible statuses you can see there are: * `alive` for a server that's...

> The Podman driver keeps track of hashes on each node to ensure the same version comes up for each task. This avoids the scenario where a single node deploys...

> Does Nomad itself keep track of which image hash is tied to a task, or otherwise allow the driver to submit metadata to Nomad in a way that can...