resource/job: set namespace on register

[FourLeafTec]

When register jobs by Http api need to set the job namespace in the request.

coder/coder#10074

[hashicorp-cla]

All committers have signed the CLA.

[lgfa29]

Hi @FourLeafTec 👋

Thank you for the PR, and apologies for the delay on getting this reviewed. I think the changes look good, but I'm curious to understand how you reached this problem.

The Nomad API should use the namespace from the job if none is set in the request:
https://github.com/hashicorp/nomad/blob/a6e164673ed5f37f010eafb8ff0adc92de195946/command/agent/job_endpoint.go#L1002-L1019

Since the provider doesn't set any WriteOptions I'm curious how you ended up with the request reported in coder/coder#10074 (comment), with the ?namespace=default query param.

[DEBUG] http: request complete: method=PUT path="/v1/jobs?namespace=default&region=global"

I have not use coder before (looks like a cool project!) but does it not use Terraform directly?

[lgfa29]

Ohh I see, I think it's the same problem as #274.

If coder is running the terraform CLI as a Nomad job, then it may be reading the NOMAD_NAMESPACE env var from that allocation.

We added the ignore_env_vars to fix this problem, so you can update your provider config to something like this:

provider "nomad" {
  ignore_env_vars = {
    "NOMAD_NAMESPACE" = true
    "NOMAD_REGION"    = true
  }
}

But setting the correct namespace sounds like a good thing to do regardless. Just watch out for the NOMAD_REGION env var 😅

[lgfa29]

Pushed a commit to also set the namespace on PlanOpts and another one to add a changelog entry.

Thank you for the contribution!