elastic / elastic/logstash

plugins https/ssl options inconsistencies

Open
#2,151 23 comments 1 reaction 0 assignees View on GitHub
breaking change enhancement
Dominant language
Java
Stars
14.9k
Forks
3.5k
Avg merge
19h 14m
Merged PRs (30d)
63

Description

We should probably look into using a standard config option for using the `https`/`ssl` protocol. I did a little survey and this is what we currently use:
- *_protocol => ['http', 'https’] - logstash-output-elasticsearch-ec2
- ssl => boolean - logstash-output-elasticsearch
- ssl => boolean - logstash-input-rabbitmq
- proto => ['http', 'https’] - logstash-output-loggly
- ssl_enable = > boolean - logstash-input-tcp
- ssl => boolean - logstash-output-redmine
- enable_ssl => boolean - logstash-output-riak

I suggest we standardize on ssl:

``` ruby
config :ssl, :validate => :boolean
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.