Vox Pupuli Tasks Repositories About
Log in

GitHub puppet-prosody
Puppet module for managing the Prosody Jabber/XMPP server

Repo Checks ( 10 of 16 successfull )
Metadata Valid
No translation
passed
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_SUPPORT_RANGE}
failed
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
passed
With Operatingsystem Support
No translation
passed
Operatingsystems
No translation
passed
Supports Only Current Ubuntu
No translation
failed
Supports Latest Ubuntu
No translation
failed
Supports Only Current Debian
No translation
passed
Supports Latest Debian
No translation
passed
In Modulesync Repo
Is listed as a module managed using modulesync_config
passed
Synced
Has a .msync.yml file
passed
Latest Modulesync
Has been synchronized with the latest tagged version of modulesync_config
failed
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
passed
Released
Is in modulesync_config and in forge releases.
passed
Valid Sync File
If a (optional) sync file is present, it must not contain a `.travis.yml` entry.
failed
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.
failed

Open Pull Requests

add Integer to print_recursive
needs-tests

Integers in Lua should not be printed as strings but as Integers !

Open PR in GitHub
fix array in print_recursive function (in both templates !)
needs-tests

Pull Request (PR) description

Rendering of Arrays used ; instead of ,
Additionally with this fix, empty array are now rendered correct.

This Pull Request (PR) fixes the following issues

Fixes #88

Open PR in GitHub
add possibility to force service and spec tests for service

Pull Request (PR) description

There are three commits, which all shall not change the current behaviour:
first add spec tests for prosody::service class, secondly simplify the prosody::service class to not have any statements depending on os facts (these should be managed with hiera).
The third one is the important one, currently service cannot be managed without setting prosody::daemonize to true. But with systemd we like to set daemonize to false (since systemd likes to run prosody in foreground) and ensure the service (eg for
reload on new certificate etc.)

This Pull Request (PR) fixes the following issues

allow ensurance of prosody service with systemd.

Additional remark

At least on Debian bullseye (and probably buster) which both use systemd by default, we should set prosody::manage_service to true. I can do an pull request for that if you wish as soon as this one is merged.

Open PR in GitHub
Introduce support for Gentoo
enhancement
needs-tests

Pull Request (PR) description

This PR introduces support for Gentoo. As packaged in net-im/prosody, Prosody uses some path which differ from the ones hardcoded in the module. This PR makes these paths configurable and it introduces the correct defaults for Gentoo.

Additionally, the community modules are packaged for Gentoo and the PR introduces support for that, too.

Open PR in GitHub
Fix rendering of nested hash inside array
tests-fail

This is needed to support externalservices options like
https://prosody.im/doc/modules/modexternal_services

Open PR in GitHub