Making Version-Check API more robust

Author: Chris Wiechmann

apibuilder4elastic/endpoints/versionLookup.json

@@ -39,18 +39,16 @@
         "operationId": "Check version",
         "parameters": [
           {
-            "type": "number",
+            "type": "string",
             "in": "query",
             "name": "filebeatVersion",
-            "description": "The filebeat version",
-            "required": true
+            "description": "The filebeat version"
           },
           {
-            "type": "number",
+            "type": "string",
             "in": "query",
             "name": "logstashVersion",
-            "description": "The logstash version",
-            "required": true
+            "description": "The logstash version"
           }
         ],
         "description": "Checks the version of Filebeat and Logstash if they are contain the expected version shipped with the API-Builder Docker-Image currently used.",

logstash/pipelines/BeatsInputPipeline.conf

@@ -38,7 +38,7 @@ filter {
       set => { "[versionChecked]" => "versionCheck" }
     }
     # Check if there is a configuration/version mismatch
-    if([versionStatus][versionStatus]=="error") {
+    if([versionStatus][versionStatus]!="ok") {
       ruby {
         code => "
           logger.info('Exit Logstash as version of Filebeat or Logstash does not match to API-Builder version. Check API-Builder logs for more details');