-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nomad_acl_token cannot unmarshal field ACLToken.ExpirationTTL with Nomad 1.5.x #312
Comments
Just to add to the report:
Same Terraform & nomad provider versions as above. Nomad cluster in version Same for both Thanks! |
Could it be related to hashicorp/nomad#16311 ? |
just got the same issue, updating the go.mod so it knows about the new changes and rebuilding the provider fixes the problem for me.
|
I'm experiencing the same issue with a new Could it be related to this fix: hashicorp/nomad#15999 |
I'm experiencing this as well in a new cluster with |
Hi everyone, to fix this I believe we will need to update the provider Nomad dependency which will happen within the next release alongside #305. |
Glad to hear that! When can we expect this release? :) |
Hi @wasilak, no concrete dates, but near-term. |
In case anyone is looking for a patch in the meantime, make sure you've run $ git clone git@github.com:hashicorp/terraform-provider-nomad.git
$ cd terraform-provider-nomad
# Update the nomad dependencies
$ go get github.com/hashicorp/nomad
$ go get github.com/hashicorp/nomad/api
# Build the updated provider
$ go build -o terraform-provider-nomad
# Copy the updated provider to the local providers cache.
#
# On Linux or Windows this will be slightly different, check the existing path to see where it should go!
$ mv terraform-provider-nomad <your project dir>/.terraform/providers/registry.terraform.io/hashicorp/nomad/1.4.19/darwin_arm64/terraform-provider-nomad_v1.4.19_x5 You may need to delete the |
Hi @kochen it's been open since Jan because I worked on it while also working on the SSO feature within the main Nomad repository. 1.5.0 has also only been GA for one week which includes that fix. We have a single remaining question on the PR before we will be able to merge it. If this takes longer than expected, then we will totally use a separate PR for just updating the dependency. I people are willing to build from main, I can update the dependency in main. Due to the release process, however, we would wait to perform an official release until all items we have lined up are merged. |
Hiya, any eta on this? The work around from @xkisu helps but is not ideal for use in our automated pipelines for configuring nomad. |
Hey @jrasell I second above, can we please push out a release with a fix? This is hampering with CI flows for which it's not easy to distribute a custom build of the provider. |
Hi all, the release is now available as v1.4.20: https://releases.hashicorp.com/terraform-provider-nomad/1.4.20/. Thanks for your patience. |
I've recently run into this issue with nomad provider v1.4.20 and Nomad version 1.4.4:
I haven't gotten a chance to look into the provider changes, but i figured this issue is relevant. Rolling back to v1.4.19 fixed the issue. |
Terraform Version
Nomad Version
Nomad 1.5.0
Provider Configuration
Environment Variables
Affected Resource(s)
Terraform Configuration Files
Debug Output
Expected Behavior
naturally it should provision the resource
Actual Behavior
The error message is displayed and the apply fails.
Steps to Reproduce
terraform init
terraform apply
Important Factoids
ACLs are bootstrapped and the bootstrap token is set in the environment vars.
The text was updated successfully, but these errors were encountered: