GitHub puppet-bareos
Puppet Module to manage bareos

Repo Checks ( 17 of 28 successfull )
Metadata Valid
No translation
passed
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_SUPPORT_RANGE}
passed
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 Debian
No translation
failed
Supports Latest Debian
No translation
failed
Supports Only Current Ubuntu
No translation
failed
Supports Latest Ubuntu
No translation
failed
Supports Only Current Centos
No translation
failed
Supports Latest Centos
No translation
failed
Supports Only Current Rocky
No translation
passed
Supports Latest Rocky
No translation
failed
Supports Only Current Almalinux
No translation
passed
Supports Latest Almalinux
No translation
failed
Supports Only Current Redhat
No translation
failed
Supports Latest Redhat
No translation
passed
Supports Only Current Fedora
No translation
passed
Supports Latest Fedora
No translation
passed
Supports Only Current Amazon
No translation
passed
Supports Latest Amazon
No translation
failed
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.
passed
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.
passed

Open Pull Requests

Allow doplet device_type
merge-conflicts
needs-tests

Will allow the use of a droplet storage backend.
Will try to get back with another PR for configuring the droplet itself.

Open PR in GitHub
add custom user groups parameter
merge-conflicts
Add support for droplet device_type

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

<!--
Allow device_type of droplet to be added. This is to support, for example, using S3 as a backend for device type.
-->

This Pull Request (PR) fixes the following issues

<!--
Fixes bareossettings function from failing, when attempting to set devicetype to droplet for the bareos-sd.d/device/droplet.conf
configuration.
-->

Open PR in GitHub
Edit heartbeat_interval variable to accept integer instead of time

Within /etc/bareos/bareos-dir.d/director/bareos-dir.conf, Heartbeat Interval accepts a value of an integer E.G 60. However, when attempting to set a value of 60 within the bareos director configuration, the below error is shown during rspec testing
ruby
Value '60' does not match regex (?i-mx:^(\d+|(\d+\W+(seconds|sec|s|minutes|min|hours|h|days|d|weeks|w|months|m|quarters|q|years|y)\W*)+)$)

puppet
class { 'bareos::director::director':
heartbeat_interval => 60
...
}

Where 60 is a valid value for the bareos-dir.conf heartbeat_interval. The values matched by Puppet's timestamp will not work here.

Open PR in GitHub
WIP

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

<!--
Replace this comment with a description of your pull request.
-->

This Pull Request (PR) fixes the following issues

<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->

Open PR in GitHub
[BREAKING CHANGE] updated default version to Bareos 21
backwards-incompatible

Pull Request (PR) description

updated default version to Bareos 21

This Pull Request (PR) fixes the following issues

Fixes #80

Open PR in GitHub
Type aliases for all the things
enhancement

Pull Request (PR) description

Introduces type aliases for all the classes.

Will remove type checking from the provider.

This Pull Request (PR) fixes the following issues

n/a

Open PR in GitHub
Add acceptance test

We have an example in this project and can run acceptance tests against it. Will it work?

Open PR in GitHub
Support Debian 11
enhancement
tests-fail
needs-tests

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

Support Debian 11

This Pull Request (PR) fixes the following issues

<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->

Open PR in GitHub
added https option for repository
needs-tests

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

added a parameter which enables https by default. can be set to false to use http without TLS

This Pull Request (PR) fixes the following issues

Fixes #70

Open PR in GitHub
Porting functions to the modern Puppet 4.x API

We noticed that your Puppet module includes Puppet 3.x function and created this
pull request to help you get started porting them to the new API.

The Puppet function API has a long history and many people in the ecosystem,
including you, took advantage of this API to extend Puppet to do some really
cool things. Unfortunately the original function API had many critical
limitations, and so Puppet introduced a new and improved API with Puppet 4.x.

Each modern Puppet 4.x function is just a little faster and just a little safer
to use, meaning that as we all port our functions over, compilation times across
the ecosystem will get more and more performant. Modern Puppet 4.x functions
have improved thread safety, memory management, and load time. Even more
importantly, they’re isolated to the environment they’re loaded from.

And as a developer, you'll see benefits like namespaced function signatures,
automatic data type checking, multiple dispatches allowing you to easily handle
different kinds of function invocations, and vastly improved code reuse.


This pull request was autogenerated and the ported functions do not yet take
advantage of the data type checking or multiple dispatches. You will want to
finish the port by making those changes and adding any documentation updates.
See this tutorial for more information.

While you're at it, double check to see if there are any functions that couldn't
be automatically ported and update them yourself.

To be extra cautious about losing data, this pull request did NOT delete the
legacy function files, so when you're satisfied with the new functions, don't
forget to delete the legacy code!

If this repo is a fork, when you're all done, you might consider contributing
your work upstream.


If you have any questions, feel free to ping me in this PR, or stop by the
Puppet Community Slack to chat. And thanks so much
for being part of our vibrant community of developers!

Open PR in GitHub