-
Notifications
You must be signed in to change notification settings - Fork 271
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
Refs #32885: Add puppet user to user_groups only if server or client certificate contains puppet path #938
Conversation
518a1b4
to
3cd393e
Compare
3cd393e
to
afaf795
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to see some spec test for this. Also, I think the word "only" is missing in the title to indicate the change. Other than that 👍
afaf795
to
b6a7f60
Compare
I added a spec test, let me know if you were also wanting an acceptance test. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should do an installer migration for this as well to remove 'puppet'
from the answers file to really benefit from this.
…certificate contains puppet path
b6a7f60
to
fa4bdb0
Compare
The change theforeman/puppet-foreman#938 introduced dynamically determining if the puppet group needed to be added to the foreman user. This no longer needs to be set explicitly on the foreman::user_groups parameter thus the migration cleans it up if present.
Here is the installer PR -- theforeman/foreman-installer#690 |
The change theforeman/puppet-foreman#938 introduced dynamically determining if the puppet group needed to be added to the foreman user. This no longer needs to be set explicitly on the foreman::user_groups parameter thus the migration cleans it up if present.
The change theforeman/puppet-foreman#938 introduced dynamically determining if the puppet group needed to be added to the foreman user. This no longer needs to be set explicitly on the foreman::user_groups parameter thus the migration cleans it up if present.
The change theforeman/puppet-foreman#938 introduced dynamically determining if the puppet group needed to be added to the foreman user. This no longer needs to be set explicitly on the foreman::user_groups parameter thus the migration cleans it up if present.
The change theforeman/puppet-foreman#938 introduced dynamically determining if the puppet group needed to be added to the foreman user. This no longer needs to be set explicitly on the foreman::user_groups parameter thus the migration cleans it up if present.
The change theforeman/puppet-foreman#938 introduced dynamically determining if the puppet group needed to be added to the foreman user. This no longer needs to be set explicitly on the foreman::user_groups parameter thus the migration cleans it up if present.
The change theforeman/puppet-foreman#938 introduced dynamically determining if the puppet group needed to be added to the foreman user. This no longer needs to be set explicitly on the foreman::user_groups parameter thus the migration cleans it up if present.
Looking for feedback here as I don't know what the exact correct answer is to prevent the following error when setting
puppet::server
to false:It feels like a user of the module should not have to explicitly configure the
user_groups
if they are settingpuppet::server
to false and that the module should adjust appropriately.The puppet-foreman_proxy seems to have a similar failure but different approach: https://github.com/theforeman/puppet-foreman_proxy/blob/941e934a4a27a40e7963bc59f6ab5c14fafb82dc/manifests/config.pp#L33