Skip to content

Conversation

@greatflyingsteve
Copy link
Contributor

Pull Request (PR) description

This is a rebase of #129 onto master (which should make all the tests pass, now, or at least it does when I run them locally).

This Pull Request (PR) fixes the following issues

Fixes #142

$file_mode = $bareos::params::file_mode,
$file_dir_mode = $bareos::params::file_dir_mode,
String $repo_release = '21',
$user_groups = $bareos::params::user_groups,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add a data type for this new parameter? Probably Array[String[1]].

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, as it is a new parameter, do not put the default value in params.pp but put it here. That way, the actual value is documented when you generate the documentation.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you don't mind, I'd like to add that as part of attempting to get #154 incorporated, as well. If you do mind, of course, I'm not opposed to adding it, here, it just feels vaguely like making a style shift like that all at once is "cleaner?"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, as it is a new parameter, do not put the default value in params.pp but put it here. That way, the actual value is documented when you generate the documentation.

I was mostly aiming to port the original author's work mostly-unmolested, but I also find the use of params.pp here icky. Is it better to try and stick with a clean rebase, or should I just go ahead and fix things While I'm In Here™?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After some discussion out-of-band, I've added updates to remove $user_groups from params.pp and add typing for the param in init.pp.

$file_dir_mode = $bareos::params::file_dir_mode,
String $repo_release = '21',
$user_groups = $bareos::params::user_groups,
String $repo_release = '22',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing the default version make it a breaking change. This is just a FYI, if the latest version is 22 we can change the default in the next (major) version. I will add a backward-incompatible label accordingly.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see #161 is about adding support for bareos 23. Do you plan to rebase this version too next?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The latest version is actually 24 - there's another PR that adds support for version 23 that I'd like to ALSO get merged, and if someone wants to cut a new (breaking) release, well, master already contains unreleased breaking changes at the moment.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 we can do a single major release that default to 24 then, I think it is sensible.

@smortex smortex added the backwards-incompatible This change will lead to a major version bump for the next release label Jun 27, 2025
Freshen code style to bring things more up to date and avoid legacy
patterns like params.pp and untyped parameters.  Includes updates to
REFERENCE.md.
@smortex smortex merged commit 41657d9 into voxpupuli:master Jun 27, 2025
5 checks passed
@smortex smortex mentioned this pull request Jun 27, 2025
@greatflyingsteve greatflyingsteve deleted the bareos-22 branch June 27, 2025 23:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backwards-incompatible This change will lead to a major version bump for the next release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Is version 22 supported ?

4 participants