-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
There is no consul CLI config option #3304
Comments
PRs for this would definitely be welcome. Could look at the Vault flags for guidance. |
I don't code in Go, sorry. |
Git jargon for "pull request". |
I would also suggest a cross-check to make sure all config file options can be done in CLI and vice-versa. |
This update introduces command line flags for all Consul options thus allowing users to both use a config file and CLI options to configure Consul. Website documentation has also been updated. Closes hashicorp#3304
@flybd5 We don't aim to have full parity with the config file. Just the most common options should be available as flags. |
I think you should. Some people like to use config files but others prefer to set up things on the command line exclusively. When setting up systemctl definition files I prefer for the config to be self-contained using the CLI. |
@flybd5 These becomes very easy in a system where some sort of configuration management system like SALT/Ansible/(even Packer) is used to deploy Consul/Nomad. Cheers, |
@shantanugadgil The point is that there is no justification to force the developer to accept one viewpoint over another. It also looks unprofessional to offer one option, but do a half-a** job of the other. The issue of config management is not relevant because you can manage systemctl files just as well as you can manage config files. Config management tools don't care about the content of the files. |
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. |
Nomad version
All
Issue
There is a way to config the info to connect to a consul client from an hcl file but not from the command line. I checked in commands.go and nothing.
The text was updated successfully, but these errors were encountered: