Hello!,

Just started working with this package and have to say is great!.

Was playing with the Supervisor class and would love to have an option specify the path where supervisorctl resides as well to be able to define where the configuration may reside.

There are some scenarios where the

In the CI automated generated docs of the control repo, we can add documentation generated automatically showing classes usage in different nodes.

On Windows, you can hit some really obscure issues when starting (h/t @missjwo), e.g. failed to create symbolic link

These are due to symlinks requiring admin on Windows. The solution is to open your console as an admin in the first place: hashicorp/vagrant#6024 (comment)

Alternatively, you can create local security policies: https://github.com/hashic

currently the server config can only be defined with nginx::resource::server. sometimes you maybe want to change the config of the server later.
for example i use "type" defines, to define server/location types for specific applications (symfony, nextcloud, wordpress, webhook, ...). these types are simple defines which contain multiple location resources to fullfill the needs of the application

It allows for using overlay2 on Centos7, even though it has kernel version 3.x (see eg. docker/docker.github.io#2558).

Docs: https://github.com/docker/docker/blob/master/docs/reference/commandline/dockerd.md#overlay2override_kernel_check.

overlay2.override_kernel_check was implemented in Docker 1.12.0-rc4 (moby/moby#24518).

The task docs are confusing in their current state. There needs to be a clearer progression through the docs from conceptual information to more practical task-based topics. A lot of the more conceptual information is currently baked into the existing docs. For example, the writing tasks doc is really huge and mixes the practical aspects of writing a task with an abundance of conceptual informatio

/kind documentation

Would look better to have a nice favicon image icon on the documentation website

We need to replace all client.post instances with requests.post in our documentation.

In the file puppet_catalog_diff_spec.rb, on line 43 shouldn't exit_code and result be reversed, according to the documentation for capture2e where result comes first and exit_code second, such as the given example stdout_and_stderr_str, status = Open3.capture2e([env,] cmd... [, opts])?

The module as it is fails to install Gunicorn on RHEL because it is provided by the RHEL Extras repository which might not be enabled on all installation .
The module doesn't ensure that RHEL Extras is enabled or even mentions it in its documentation.
Adding the provider and maybe a require to the Exec installing pip would do it

  provider => 'pip',

[Gunicorn package declaratio

My apologies in advance if this is too basic of a question, but... how would one go about installing this for use on their puppetserver? Some examples in the documentation would be most helpful - "how to get this onto a puppetserver so hiera queries are enabled", "how to get this onto your local development workstation so the face is usable", "this is how to get it to play nice with Hiera 5", etc

Describe the bug
pdk validate is missing a newline at the end, resulting in the shell prompt being printed on the same line

To Reproduce

user@machine:~/some/path/$ pdk validate
pdk (INFO): Using Ruby 2.5.7
pdk (INFO): Using Puppet 6.14.0
pdk (INFO): Running all available validators...
┌ [✔] Running metadata validators ...
├── [✔] Checking metadata syntax (metadata.json

Affected Puppet, Ruby, OS and module

For auto generated tests that contain references to variables $param1 that are also parameters we should just reference the params block instead of inserting the variable in in the test.

in #246, we merged an option (allowunconfigured) to change the hard-coded state of allow_unconfigured

This option is not mentioned in the README and should be renamed to allow_unconfigured.

Additionally we should consider the same as in #238.
If this issue is fixed before the next release, we don't have to make backwards-compatibility considerations.

(Thanks for such a great tool !)

I'm trying to set onceover up on my control repo. I have parameters to pass to my profiles, and was looking for examples of spec tests, like spec/classes/my_profile_spec.rb.

Does any one know where to find some of them ?

The repl should display documentation of each function so the user doesn't have to leave the repl session to find out how to use it.