Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow setting file group owner #231

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

arthurbarton
Copy link
Contributor

Add new optional parameter to set the group ownership of shipped files

Some Operating Systems (a current OpenBSD release) don't have group 'root' - this PR allows setting the group to something else.
Default of group:root has not changed

This Pull Request (PR) fixes the following issues

N/A

metadata.json Outdated Show resolved Hide resolved
@@ -1,6 +1,6 @@
{
"name": "puppet-letsencrypt",
"version": "5.0.1-rc0",
"version": "6.0.1-rc0",
Copy link
Member

Choose a reason for hiding this comment

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

I don't think this is a major version.

Copy link
Member

Choose a reason for hiding this comment

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

yes. please don't update the version. we do this during the next release.

@ekohl ekohl requested a review from igalic September 28, 2020 09:44
@@ -23,6 +24,7 @@
Integer $propagation_seconds = 10,
Stdlib::Absolutepath $config_dir = $letsencrypt::config_dir,
Boolean $manage_package = true,
String $ini_file_owner_group = $letsencrypt::root_file_owner_group,
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
String $ini_file_owner_group = $letsencrypt::root_file_owner_group,
String[1] $ini_file_owner_group = $letsencrypt::root_file_owner_group,

Letsencrypt::Cron::Hour $cron_hour = $letsencrypt::renew_cron_hour,
Letsencrypt::Cron::Minute $cron_minute = $letsencrypt::renew_cron_minute,
Letsencrypt::Cron::Monthday $cron_monthday = $letsencrypt::renew_cron_monthday,
String $hook_file_owner_group = $letsencrypt::root_file_owner_group,
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
String $hook_file_owner_group = $letsencrypt::root_file_owner_group,
String[1] $hook_file_owner_group = $letsencrypt::root_file_owner_group,

@@ -50,7 +50,8 @@
{
"operatingsystem": "OpenBSD",
"operatingsystemrelease": [
"6.2"
"6.6",
Copy link
Member

Choose a reason for hiding this comment

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

mhm, is this a backwards incompatible change if we drop 6.2?

Copy link
Contributor

Choose a reason for hiding this comment

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

i reckon that the latest supported versions are the last two, so it's more like a cleanup

Copy link
Member

Choose a reason for hiding this comment

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

Indeed. I think it also didn't really break compatibility with 6.2. That's just an EOL OS.

Copy link
Contributor

@igalic igalic left a comment

Choose a reason for hiding this comment

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

my issue with this PR is that we're introducing 4(?) parameters for 1 setting that was previously barely variable, or parametrisable.

so how about we just call this root_group, and be done with it?

how big is the chances that people will want to change this from the root (wheel) group to something else?

@ekohl
Copy link
Member

ekohl commented Sep 28, 2020

Btw, an alternative is to use the gid (0) instead of name. The gid is constant between Linux/BSD and avoids the need for a parameter.

@vox-pupuli-tasks
Copy link

Dear @arthurbarton, thanks for the PR!

This is Vox Pupuli Tasks, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase?

You can find my sourcecode at voxpupuli/vox-pupuli-tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants