-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Enable ability to send username/password for Basic Auth in service check stanza #2924
Comments
Looks like there is support in Consul as of late: hashicorp/consul#3107 Should allow headers in Nomad as well. |
Thanks @dadgar. Unfortunately it seems header in check is not valid?
Config below:
If you can provide some guidance on what needs to be done; I'll take a stab at doing a PR --> I'm a Golang noob :) I see in the Consul docs, the example for header is like below:
so does the resulting output will have to be as below; correct?
|
Changesets: - Simplify config with Docker; had to up the memory as JVM minimum memory is 2Gb! - Adjust listening ip to all interface so that cluster discovery works - Tried to handle authentication for ES endpoints but fail TODO: Once hashicorp/nomad#2924 is fixed; need to send in the
@leowmjw Ah sorry to confuse you! I was agreeing that we should add support. It isn't there currently. Hopefully in 0.6.1 or 0.6.2 |
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 v0.6
Request for ability to pass username/password for Basic Auth in the service check stanza. As example, I have below where it checks the cluster endpoints for ElasticSearch:
As cannot authenticate; will hit error below:
Thanks for any possible guidance. Thanks!
The text was updated successfully, but these errors were encountered: