-
-
Notifications
You must be signed in to change notification settings - Fork 254
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
change group for user_install #242
Comments
|
I've confirmed with inspec that this isn't the case. So I'm a little confused how you're setting the value! See this test for how I'm setting the group: https://github.com/sous-chefs/ruby_rbenv/pull/245/files#diff-2f1fd653c59c431dfe5f42fd9c8c5fdc And here for me testing for the correct group: https://github.com/sous-chefs/ruby_rbenv/pull/245/files#diff-817b63b0dbded23627f5495795b18289 |
Hi @damacus thank you so much for taking this for a review. My case was the group of the user is different and they are not alike. E.g vagrant:adminuser not vagrant:vagrant Here are my concerns: let me know if i am using the resource correctly But i want is: ruby_rbenv resource
for what's happening: The output of that resource becomes
Im using these resource and needing it to override the group as there are cases that user and group are not the same:
in my case if the service account group is available in the node, it should override the group. if false, it will use the normal user which has the same group as user. e.g
|
Hi @damacus, Still not working, the cookbook can't see ldap group even its specified on resource rbenv_user_install. the group that stated in
And then throws me an exception below, and it seems the resource still using the user as the the group
Although it works if i remove this:
To become:
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Cookbook version
2.1.2
Chef-client version
14.4.56
Platform Details
Rhel 7
Scenario:
property :group, String, default: lazy { user }
Is it possible that it can have a feature for custom group? it seems that it defaults to user.
The case is what if we want to use rbenv on a user:chefadmins instead of user:user
The text was updated successfully, but these errors were encountered: