logstash-input-http 0.0.1 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 032fe90380dce11dd20661a8aac9084aeaf1d98c
-  data.tar.gz: 4d54c4885e13df803bb65be27fadab2ffce058dc
+  metadata.gz: e3ef94ce2c9c91d5297661dfc7a45bc14460519f
+  data.tar.gz: e32e3fc140f3c393ee4706478cd7a01d989877a3
 SHA512:
-  metadata.gz: bc1a5f6af20ffee231471deb4f3f424c60891053acdb89d9b6c88e53c5775874af31451322f812631e1ec7d1a8522692a51647b9ab34a4dc349b20a4972a073b
-  data.tar.gz: d6f67bf01ae8bc102de7eb14bb877a03daacb99d27367e4805343540d5f8ad8d778ac1bfc74b45982a68c5fe3f5ffe8916ebd4f9e95591583c3e193cda6472eb
+  metadata.gz: d4631608a1130879d51dcc9a0a579524615231e1b9c8eb47dcd5ff5b1d0377703bda0efd2f88310825222194246652659641cb77cfa1b2f857793330bfb1e32c
+  data.tar.gz: 6a45315540c7908de5e106c49f35ee236abfa0f55fb0e7eccdaa67d64007eaa133b438fe60925e62f39f89b2d2be0bd8cbccdc96eff808a6528fd7bd95dd2b12

data/CHANGELOG.md

@@ -0,0 +1,4 @@
+## 1.0.0 (July 1, 2015)
+
+* First version: New input to receive HTTP requests
+* Added basic authentication and SSL support

data/NOTICE.TXT

@@ -0,0 +1,5 @@
+Elasticsearch
+Copyright 2012-2015 Elasticsearch
+
+This product includes software developed by The Apache Software
+Foundation (http://www.apache.org/).

data/lib/logstash/inputs/http.rb

@@ -11,26 +11,47 @@ class Puma::Server
   def normalize_env(env, client); end
 end
 
-# This output opens a web server and listens to HTTP requests,
-# converting them to LogStash::Event instances.
+# Using this input you can receive single or multiline events over http(s).
+# Applications can send a HTTP POST request with a body to the endpoint started by this
+# input and Logstash will convert it into an event for subsequent processing. Users 
+# can pass plain text, JSON, or any formatted data and use a corresponding codec with this
+# input. For Content-Type `application/json` the `json` codec is used, but for all other
+# data formats, `plain` codec is used.
+#
+# This input can also be used to receive webhook requests to integrate with other services
+# and applications. By taking advantage of the vast plugin ecosystem available in Logstash
+# you can trigger actionable events right from your application.
+# 
+# ==== Security
+# This plugin supports standard HTTP basic authentication headers to identify the requester.
+# You can pass in an username, password combination while sending data to this input
+#
+# You can also setup SSL and send data securely over https, with an option of validating 
+# the client's certificate. Currently, the certificate setup is through 
+# https://docs.oracle.com/cd/E19509-01/820-3503/ggfen/index.html[Java Keystore 
+# format]
 #
 class LogStash::Inputs::Http < LogStash::Inputs::Base
+  #TODO: config :cacert, :validate => :path
+
   config_name "http"
 
-  # If undefined, Logstash will complain, even if codec is unused.
+  # Codec used to decode the incoming data.
   default :codec, "plain"
 
-  # Which host or ip to bind to
+  # The host or ip to bind
   config :host, :validate => :string, :default => "0.0.0.0"
 
-  # Which TCP port to bind to
+  # The TCP port to bind to
   config :port, :validate => :number, :default => 8080
 
   # Maximum number of threads to use
   config :threads, :validate => :number, :default => 4
 
-  # Basic Auth
+  # Username for basic authorization
   config :user, :validate => :string, :required => false
+
+  # Password for basic authorization
   config :password, :validate => :password, :required => false
 
   # SSL Configurations
@@ -41,13 +62,11 @@ class LogStash::Inputs::Http < LogStash::Inputs::Base
   # The JKS keystore to validate the client's certificates
   config :keystore, :validate => :path
 
-  #TODO: config :cacert, :validate => :path
-
   # Set the truststore password
   config :keystore_password, :validate => :password
 
-  # here you can describe how to decode specific content-types
-  # by default the default codec will be used
+  # Here you can set how to decode specific content-types in the body of the request.
+  # By default, the plain codec will be used
   config :additional_codecs, :validate => :hash, :default => { "application/json" => "json" }
 
   # useless headers puma adds to the requests

data/logstash-input-http.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |s|
   s.name = 'logstash-input-http'
-  s.version         = '0.0.1'
+  s.version         = '1.0.0'
   s.licenses = ['Apache License (2.0)']
   s.summary = "Logstash Input plugin that receives HTTP requests"
   s.description = "This gem is a logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/plugin install gemname. This gem is not a stand-alone program"

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: logstash-input-http
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 1.0.0
 platform: ruby
 authors:
 - Elastic
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2015-06-17 00:00:00.000000000 Z
+date: 2015-06-29 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: logstash-core
@@ -125,6 +125,7 @@ files:
 - DEVELOPER.md
 - Gemfile
 - LICENSE
+- NOTICE.TXT
 - README.md
 - Rakefile
 - lib/logstash/inputs/http.rb
@@ -152,7 +153,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project:
-rubygems_version: 2.4.5
+rubygems_version: 2.2.2
 signing_key:
 specification_version: 4
 summary: Logstash Input plugin that receives HTTP requests