Skip to content
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

Parse Environment Variables in Agent Config Files #1870

Closed
stongo opened this issue Oct 26, 2016 · 5 comments
Closed

Parse Environment Variables in Agent Config Files #1870

stongo opened this issue Oct 26, 2016 · 5 comments

Comments

@stongo
Copy link

stongo commented Oct 26, 2016

To make deploying nomad easier in containerland, parse environment variables in configuration files

@stongo stongo changed the title Parse Environment Variables in Config Files Parse Environment Variables in Agent Config Files Oct 26, 2016
@stongo
Copy link
Author

stongo commented Oct 26, 2016

it's been suggested I use consul-template instead. but this is not a viable replacement. for example, the configuration item advertise in nomad agent. In coreos I can pass the environment variable COREOS_PRIVATE_IPV4 as a docker run environment variable to easily set this rather than hardcoding it. using consul-template wouldn't solve this use case. instead I'll have to use sed on the config file in a docker container start script to accomplish this.

@diptanu
Copy link
Contributor

diptanu commented Oct 26, 2016

@stongo We will revamp how we read configuration from HCL files. It's going to come up sometime in the future, but less of a priority right now since we have some higher priority stuff to take care of over the next few months.

@v-byte-cpu
Copy link

3.5 years passed and no progress ?

@tgross tgross added this to Needs Roadmapping in Nomad - Community Issues Triage Feb 12, 2021
@tgross
Copy link
Member

tgross commented Mar 4, 2021

Shipped in Nomad 1.0 with HCL2.

@tgross tgross closed this as completed Mar 4, 2021
Nomad - Community Issues Triage automation moved this from Needs Roadmapping to Done Mar 4, 2021
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants