puppet nftables

* We only take pull requests with passing tests, and documentation. [travis-ci](http://travis-ci.org) runs the tests for us. You can also execute them locally. This is explained [in a later section](#the-test-matrix).

bundle exec rake beaker

```

This will run the tests on the module's default nodeset. You can override the

nodeset used, e.g.,

```sh

BEAKER_set=centos-7-x64 bundle exec rake beaker

```

There are default rake tasks for the various acceptance test modules, e.g.,

```sh

bundle exec rake beaker:centos-7-x64

bundle exec rake beaker:ssh:centos-7-x64

```

If you don't want to have to recreate the virtual machine every time you can

use `BEAKER_destroy=no` and `BEAKER_provision=no`. On the first run you will at

least need `BEAKER_provision` set to yes (the default). The Vagrantfile for the

created virtual machines will be in `.vagrant/beaker_vagrant_files`.

Beaker also supports docker containers. We also use that in our automated CI

pipeline at [travis-ci](http://travis-ci.org). To use that instead of Vagrant:

```sh

PUPPET_INSTALL_TYPE=agent BEAKER_IS_PE=no BEAKER_PUPPET_COLLECTION=puppet6 BEAKER_debug=true BEAKER_setfile=debian10-64{hypervisor=docker} BEAKER_destroy=yes bundle exec rake beaker

The easiest way to debug in a docker container is to open a shell:

```sh

docker exec -it -u root ${container_id_or_name} bash

```