Update the Nomad provider for new job features

[shantanugadgil]

Terraform Version

0.11.8

Affected Resource(s)

• nomad_job

Expected Behavior

At any given time, the Nomad provider should have all the features of the latest version of Nomad (v0.8.6 at the time of this bug report)

Actual Behavior

Terraform's Nomad provider is lagging behind.

Important Factoids

We (and I assume many other folks) would like to codify their entire usage via Terraform.
The Terraform provider not being able to do many things makes for out-of-band activities like directly having to do nomad plan, nomad run, etc.

Using the command line is fine for folks who are very familiar with the Nomad options.
All-in-all, it is easier to direct folks to a single "interface" (i.e. Terraform, than to have to learn multiple commands and options)

Thanks and Regards,
Shantanu

[epetrovich]

There is a lot of pain in the ss

• nomad_job.blitzops-app-dispatch: 1 error(s) occurred:
• nomad_job.blitzops-app-dispatch: error parsing jobspec: error parsing 'job': 1 error(s) occurred:
• group: 'blitzops-group' -> invalid key: reschedule

[epetrovich]

@paddycarver Please!

[cgbaker]

Hi all, I am looking into this right now. I will have an update on this ASAP. Thank you for your patience.

[epetrovich]

@cgbaker
I hope you're not in the another time-space dimension )

[cgbaker]

I'm in Florida... does that count? 😄

[mildred]

Yep, got errors too, at first I thought that the nomad versions I used on my servers was lagging behind, but no, it was here :)

group: 'main', task: 'main', service (0) -> invalid key: canary_tags

[mildred]

Are there plans to have this provider always in sync (perhaps a new release of this provider on each new nomad release) ?

[cgbaker]

We are planning to keep the Terraform provider working with new releases of Nomad, either by updating the provider on Nomad releases or by modifying the provider so that it is unversioned/generic.

…

On Wed, Nov 7, 2018, 02:29 mildred ***@***.*** wrote: Are there plans to have this provider always in sync (perhaps a new release of this provider on each new nomad release) ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#46 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABmPTyOfIOdb2tsSgRyRn5hwGZ_biqmuks5usrX3gaJpZM4XMN0d> .

[mildred]

Thanks.

For those interested, I could build the last version of the nomad provider using nomad 0.8.6 with this Dockerfile:

FROM golang:1.11 AS terraform-nomad
ARG NOMAD_VERSION=0.8.6
ARG TERRAFORM_NOMAD_VERSION=1.2.0
RUN go get github.com/kardianos/govendor
WORKDIR /go/src/github.com/terraform-providers/terraform-provider-nomad
RUN git clone -b v${TERRAFORM_NOMAD_VERSION} https://github.com/terraform-providers/terraform-provider-nomad.git .
RUN govendor fetch -v github.com/hashicorp/nomad/...@v${NOMAD_VERSION}
RUN govendor fetch -v github.com/hashicorp/golang-lru/...
RUN make build

[shantanugadgil]

@cgbaker

Would you be releasing an updated version which works with Nomad 0.8.6 syntax, and then an updated one when the 0.9 alpha/beta releases happen (hopefully soon)

[cgbaker]

Yes and yes.

…

On Wed, Nov 7, 2018, 08:26 Shantanu Gadgil ***@***.*** wrote: @cgbaker <https://github.com/cgbaker> Would you be releasing an updated version which works with Nomad 0.8.6 syntax, and then an updated one when the 0.9 alpha/beta releases happen (hopefully soon) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#46 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABmPT6LnvsI6JJVlysWTnxXdmQTY1RqAks5uswmggaJpZM4XMN0d> .

[shantanugadgil]

when? and when?

Based on the disturbance in the force (flurry of activity) I sense Consul 1.4.0 or Nomad 0.9.0 (rc1?) is coming and people could be busy! ☺️☺️☺️

[cgbaker]

We're going to get the update for 0.8.6 out immediately just by updating the dependencies, as folks have been doing in this thread. Then we'll work on un-versioning the client in the provider so that we don't have to keep working, err, ignoring it. The plan is to have that ship soon after the 0.9.0 release (if not before).

…

On Wed, Nov 7, 2018 at 11:59 AM Shantanu Gadgil ***@***.***> wrote: when? and when? Based on the disturbance in the force (flurry of activity) I sense Consul 1.4.0 or Nomad 0.9.0 (rc1?) is coming and people could be busy! ☺️☺️☺️ — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#46 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABmPT-kSK4i-T5tnPyyvsHliih758b57ks5uszu9gaJpZM4XMN0d> .

[ketzacoatl]

@cgbaker, thanks for the updates! Was there a release made for the provider, updated to work with 0.8.6?

[cgbaker]

Not yet, but soon (hopefully next week).

…

On Thu, Nov 22, 2018, 14:58 ketzacoatl ***@***.*** wrote: @cgbaker <https://github.com/cgbaker>, thanks for the updates! Was there a release made for the provider, updated to work with 0.8.6? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#46 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABmPT1tV3uS_og4vxfkbFfaZmWD2XjnVks5uxw__gaJpZM4XMN0d> .

[pashinin]

Had an error about canary_tags. I don't understand it. Why all this validation is not made by Nomad itself? If there is some code from Nomad in this project that validates jobs - there always be difference about what Nomad thinks is valid and what terraform-provider-nomad thinks is valid.

I don't know but is it really this provider's job to check Nomad jobs (I mean should it be in codebase of this project)?

[lawliet89]

It parses and deserializes the jobspec into some form that the API can consume, is my guess.

The Job API wants the Jobspec in JSON form.

[cgbaker]

@pashinin , as stated above, the provider is currently "versioned" because of the client that it imports from the Nomad project. The plan is to remove this versioning so that the provider does not need to be constantly updated as new features are added to Nomad.

[pashinin]

@cgbaker really waiting for this. Thanks for answers.

[cgbaker]

My pleasure. My apologies for the delay on taking care of this.

[shantanugadgil]

I am (and have been) waiting for 0.9 GA build. :) :)

[ketzacoatl]

@cgbaker Is there a release coming for this provider to work with nomad 0.8.6?

[cgbaker]

Hopefully next week... There just a few more merge requests I want to pull in.

…

On Thu, Dec 13, 2018, 11:06 ketzacoatl ***@***.*** wrote: Is there a release coming for this provider to work with nomad 0.8.6? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#46 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABmPTx5Cdo7Uz_JHcAhra-bWE5uKZE0Sks5u4qUcgaJpZM4XMN0d> .

[ketzacoatl]

@cgbaker would it be reasonable to push a release now with what's ready to go, and then again when there are more PRs merged? Or are there updates that need to block the release?

[cgbaker]

It is my only task for today. I'm doing some manual testing right now and then I'll do the release.

[cgbaker]

v1.3.0 of the Nomad provider just released, with support for the Nomad v0.8.6 API. Thank you for your patience, I promise you that we will be much faster in adding support in the future. Please let me know if you encounter any problems with this provider.