{"action":"created","issue":{"url":"https://api.github.com/repos/elastic/elasticsearch/issues/15586","labels_url":"https://api.github.com/repos/elastic/elasticsearch/issues/15586/labels{/name}","comments_url":"https://api.github.com/repos/elastic/elasticsearch/issues/15586/comments","events_url":"https://api.github.com/repos/elastic/elasticsearch/issues/15586/events","html_url":"https://github.com/elastic/elasticsearch/issues/15586","id":123396245,"number":15586,"title":"The practicalities of forcing interactive mode for \"${prompt.*}\"","user":{"login":"joshuar","id":7401,"avatar_url":"https://avatars.githubusercontent.com/u/7401?v=3","gravatar_id":"","url":"https://api.github.com/users/joshuar","html_url":"https://github.com/joshuar","followers_url":"https://api.github.com/users/joshuar/followers","following_url":"https://api.github.com/users/joshuar/following{/other_user}","gists_url":"https://api.github.com/users/joshuar/gists{/gist_id}","starred_url":"https://api.github.com/users/joshuar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joshuar/subscriptions","organizations_url":"https://api.github.com/users/joshuar/orgs","repos_url":"https://api.github.com/users/joshuar/repos","events_url":"https://api.github.com/users/joshuar/events{/privacy}","received_events_url":"https://api.github.com/users/joshuar/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/elastic/elasticsearch/labels/discuss","name":"discuss","color":"fbca04"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-12-22T02:05:38Z","updated_at":"2016-01-10T18:11:22Z","closed_at":null,"body":"We currently allow users to specify `${prompt.text}` and `${prompt.secret}` in their `elasticsearch.yml` which will cause Elasticsearch to prompt on start-up for the value to use.  However, as part of this, we also require Elasticsearch to be run in an interactive terminal, i.e., one that a human is controlling.  \r\n\r\nHow is this meant to work in practice?  Are we expecting users to log into every node in the cluster and type the same values in?  This doesn't seem to scale.  Many users have strict security requirements around not storing passwords on disk (i.e., PCI compliance) and need to make use of this feature in an automated fashion.  In some cases they have a app that can provide the password automatically, but we're not allowing them to utilise that easily.\r\n\r\nWhat's the reasoning around forcing the use of `${prompt.*}` only on interactive terminals?  If we want to enforce this, maybe we need to show an example in our docs on how to use this without human input?\r\n\r\n "},"comment":{"url":"https://api.github.com/repos/elastic/elasticsearch/issues/comments/170376343","html_url":"https://github.com/elastic/elasticsearch/issues/15586#issuecomment-170376343","issue_url":"https://api.github.com/repos/elastic/elasticsearch/issues/15586","id":170376343,"user":{"login":"clintongormley","id":56599,"avatar_url":"https://avatars.githubusercontent.com/u/56599?v=3","gravatar_id":"","url":"https://api.github.com/users/clintongormley","html_url":"https://github.com/clintongormley","followers_url":"https://api.github.com/users/clintongormley/followers","following_url":"https://api.github.com/users/clintongormley/following{/other_user}","gists_url":"https://api.github.com/users/clintongormley/gists{/gist_id}","starred_url":"https://api.github.com/users/clintongormley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/clintongormley/subscriptions","organizations_url":"https://api.github.com/users/clintongormley/orgs","repos_url":"https://api.github.com/users/clintongormley/repos","events_url":"https://api.github.com/users/clintongormley/events{/privacy}","received_events_url":"https://api.github.com/users/clintongormley/received_events","type":"User","site_admin":false},"created_at":"2016-01-10T18:11:22Z","updated_at":"2016-01-10T18:11:22Z","body":"Your password would then be available to anybody who can run that command?  if that's the case, then why not just put it in the config file."}}