Tim Gross

This would be a nice external / third-party tool (or Nomad Enterprise feature), but yeah we could totally bootstrap this on top of Variables. You'd need to keep the HCL...

> Again this is seen only on Windows server nodes and not on linux nodes (atleast in our case) Yeah, the security update in 1.6.7 has significantly different implementation on...

Thanks @pavanrangain! Sorry to get back so slowly on this. I just wanted to pop in and say we haven't forgotten you but I've been swamped with a couple of...

Hi @DTTerastar! We have a solid idea of the problem, which is a difference in ambient credentials between running Nomad as a Windows service vs otherwise (which is what all...

Additional repro that I've closed as a dupe, but just in case there's anything useful in the logs: https://github.com/hashicorp/nomad/issues/16739

I've been digging into this one and it's not clear to me that we need or want this field. We've already got [`check.expose`](https://developer.hashicorp.com/nomad/docs/job-specification/check#expose) which generates the appropriate `expose` block for...

Hi @Trojan295! This does look similar to #5498 which was closed by https://github.com/hashicorp/nomad/pull/10404. Have you tried using the go-sockaddr syntax that's now available to pick the specific IP address you...

It's been a month or so since we've asked for more info on this, and it otherwise looks like a duplicate, so I'm going to close this one out.

Hi @freef4ll! I was able to reproduce this as you've shown here. Weirdly, I can only reproduce when there are _both_ multiple allocations and multiple `artifact` blocks. Here's the client...

@mmcquillan I've been looking at this PR as part of the rest of the Consul API update work, and it's not clear to me this makes sense to for anything...