[bugfix] Add Matching resource to NewGossConfig()

[OmarDarwish]

Fixes #278

[aelsabbahy]

Looks good. Can you add a test for this in the integration-tests folder?

[OmarDarwish]

Added. When I ran it locally, the tests I added pass for all architectures. The only failure was for the autofs service on . It was not running for precise-64. Not sure why, but it seems unrelated to my changes:

++ docker_exec /goss/precise/goss-linux-amd64 --vars /goss/vars.yaml -g /goss/precise/goss.yaml validate
++ docker exec goss_int_test_precise_amd64 /goss/precise/goss-linux-amd64 --vars /goss/vars.yaml -g /goss/precise/goss.yaml validate
+ out='.........................F........................................................

Failures/Skipped:

Service: autofs: running:
Expected
    <bool>: false
to equal
    <bool>: true

Total Duration: 1.005s
Count: 82, Failed: 1, Skipped: 0'

[OmarDarwish]

Looks like it passed on Travis though 🤷‍♂️

[elliotweiser]

@OmarDarwish I've encountered that as well when attempting to reproduce the integration test suite on my laptop. There appear to be several differences between the Travis CI environment and Docker for Mac on a development laptop that makes it difficult to reproduce. To name a few:

• Package version differences on several docker containers
• Autofs not running on the precise container
• Archlinux not starting correctly

Definitely worth investigating, but in a separate change/thread.

[aelsabbahy]

Seen it myself (fedora laptop), haven't followed up on it. I've been using Travis CI as a source of Truth.

I'm guessing it's related to the storage driver for docker on Ubuntu.