Prototype tests for salt-test-runner.
Make the grok conditional on contents of @message

This avoids having _grokparsefailure in the logs. The other option is that we could just let grok do its thing and add `tag_on_failure => []`

(break_on_match only works if all the groks are in one block)
Update metadata.yml
Update metadata.yml
Update metadata.yml
When running tests don’t use normal logstash inputs

Without this we ended up with the test process picking up events from beaver or syslog on the host.

This also means that the main logstash daemon can still be running when we execute the tests
Add apparmor tests

Note that this expects logs to come via the kernel logging facility. Most of the time though we also deploy auditd and as a result the messages will come via /var/log/audit.log, so the test suite should be updated to test both cases
Vagrant functional-test environment

Use vagrant and its salt-minion support to create a suitable
environment for running the custom-test rspec suite.

Added instruction on how to do this to the README.
Vagrant .gitignore
Merge branch 'master' into unit-tests

Conflicts:
	metadata.yml
Merge pull request #23 from ministryofjustice/unit-tests

Add functional tests for logstash syslog config; framework for others