Move from static parser to a dynamic parser

[BuddhiWathsala]

Purpose

Resolve #56.

Goals

Previously we had that static parser which created as an operator prerequisite. If a user implements a custom extension the user unable to deploy apps in K8s since this static parser does not include that custom extension.

Approach

Here we integrate parser service to Siddhi runner and use it dynamically. At the Siddhi operator runtime, it runs as follow.

• Starts the runner deployment with special system property (-Dsiddhi-parser)
• Check health and call the parser
• Retrieve parsed app and deploy
• Remove the parser

Automation tests

• Integration tests

  Update the E2E tests

Samples

Upgrade YAML examples to m2 version.

Test environment

minikube version: v1.2.0