-
Notifications
You must be signed in to change notification settings - Fork 783
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
Support Nomad Variables #1632
Support Nomad Variables #1632
Conversation
Is it upstream yet? We can do a commit-id update for now if necessary. Do you want these merged before the 0.29.2 release I'm planning for this week? |
Everything we need to support this in the API is on
Maybe we hold off on that? When I sent @angrycub off on this particular adventure 😀 I wasn't keeping in mind the beta. We can always pin to a commit-id on the Nomad side for the beta release and then if there's anything that comes up in the beta window where we really hate the API and need to change it, we're not causing regressions on a released version of So what do you (@eikenb and @angrycub) think about the following:
That'll prevent Nomad from causing extra release schedule pressure for y'all, and give us a little breathing room around the Nomad 1.4.0 beta as well. |
Thanks @tgross. Sounds like a good plan. |
b2ea0b1
to
cf2b3d2
Compare
21d2c9b
to
5ad4f2c
Compare
I've opened hashicorp/nomad#14762 with a reminder to ourselves to update Nomad to point to the new release of CT once this has been merged. |
be2fb1f
to
61e288a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks good except that one file. Thanks.
@angrycub... could you rebase on main/HEAD to get the go.mod build changes? This should allow the tests to pass (or at least fix what's currently failing). Thanks. |
@angrycub @eikenb I've just pushed a branch https://github.com/hashicorp/consul-template/tree/pinned-for-nomad-1.4.1 which is at commit 61e288a, which is what Nomad's go.mod is pinned to as of right now. That'll let us rebase/squash this PR and get the tests green before merging without interfering with the ongoing Nomad builds before we have a PR to bump the dependency. We can delete the branch so the commit gets GC'd after we've finished shipping 1.4.2. |
Nomad SV: Add Test helpers Nomad SV: Secure Variables List dependency Nomad SV: Secure Variables Get dependency Nomad SV: Add template functions Add test for variable value leak via error Add variable values to redactinator Support Namespace and Region for SV Upgrading Nomad API version to v1.4.1 Fix copypasta in Nomad configuration
5a415f5
to
5244d28
Compare
This PR extends consul-template to support NomadVariables. It adds 4 additional functions:
There is a circular dependency issue with Nomad, so the tests won't pass until Nomad has released a version that contains secure variables. I'm not sure how exactly to manage this, but I need to get the PR up at least.