logstash loses ability to use variables if ilm_policy is enabled in the output section.

[lpasquali]

For some Elastic decision, log stash "output" configuration stanza can't get variable expansion if a ilm_policy is set in the logstash output so autoation of index rotation policies and rollover is not doable at logstash level:

    output {
      elasticsearch {
        #ilm_rollover_alias => '%{[@metadata][beat]}'
        #ilm_policy => "default-geoserver-policy"
        index => "%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}"
        hosts => [ "${ES_HOSTS}" ]
        user => "${ES_USER}"
        password => "${ES_PASSWORD}"
        cacert => '/etc/logstash/certificates/ca.crt'
      }
    }

right now we can't setup a default-geoserver-policy from logstash, we should find a workaround to at least automate this with a script.