Discovery settings in elasticsearch.yml.erb about elasticsearch HOT 4 CLOSED

Ryan, could you post a (sanitized) data_bags/elasticsearch/aws.json so I understand the issue better?

from elasticsearch.

Here's an analogue to my data bag (I actually tweaked the attributes to use an encrypted databag):

{
  "id": "elasticsearch",
  "cloud": {
    "ec2": {
      "security_group": "SOMETHING"
    },
    "aws": {
      "secret_key": "SECRET",
      "access_key": "ACCESS"
    }
  }
}

As I do have an ES security group, but am not yet running an ES cluster. This produces a YAML config of:

  ec2.groups: SOMETHING

(without a 0-level indent member discovery) instead of:

discovery:
  type: SOMETHING
  ec2.groups: SOMETHING

which causes a YAML config error.

So, I think it's fair to say you just must have discovery set if you set ec2.groups, but it could be more permissive in case someone sets the cloud.ec2 and not discovery. Totally up to you, and once again -- thanks for the great cookbook and responsiveness to issues!

from elasticsearch.

Hello Ryan,

see f1fc6ef, I think it's fair to use full namespaces in the YAML file, which makes everything more resilient, and the readability does not suffer too much :)

from elasticsearch.

The full namespaces work well, and don't get in to tortured "if-this-then-that-but-not..." template conditionals. Great idea. Thanks!

from elasticsearch.