METRON-947 [DO NOT MERGE UNTIL METRON-942] Stellar Management Function for Metron Parser Extension Configurations

[ottobackwards]

METRON-777 adds the Metron Extension capability, the default parsers as extensions, and the parser archetype
METRON-942 adds metron-rest support for installing and uninstalling parser extensions, as well as the configuration primitives for extensions in zookeeper

This PR adds a Stellar Management command to retrieve those configurations.

Testing

Build and install some parser extensions

Follow the test plan for METRON-942, to the point where you have built and installed one or more parser extensions.

deploy the metron-management jar per readme

Run Stellar

[vagrant@node1 ~]$ /usr/metron/0.4.0/bin/stellar  -z node1:2181

Run the command:

CONFIG_GET('PARSER_EXTENSION', 'metron-parser-nice-assembly-0_4_0')

verify that the configuration return matches what you would see in the rest client
if you executed Parser Extension Controller : get /api/v1/ext/parsers/{name} -> name = metron-parser-nice-assembly-0_4_0

For all changes:

• [ x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
• [ x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
• [x ] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

• [na ] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

• [ x] Have you included steps or a guide to how the change may be verified and tested manually?

• [x ] Have you ensured that the full suite of tests and checks have been executed in the root incubating-metron folder via:

  mvn -q clean integration-test install && build_utils/verify_licenses.sh 
  

• [x ] Have you written or updated unit tests and or integration tests to verify your changes?

• [ na] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

• [ x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

• Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:

  cd site-book
  mvn site
  

Note:

Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

[ottobackwards]

I am closing this PR, I'll re-submit when METRON-942 is landed