Closed kbrock closed 1 year ago
@kbrock will we also need to do this (add user and chgrp) in the rpm build for existing appliances?
sounds like we should move all of this over to the rpms
the rpm now has the manageiq user.
Wondering if we want to transition the appliance to using the manageiq user or another one. I'd actually prefer admin
rather than using manageiq
but that may be introducing too many special accounts.
Thinking we don't want our service user to be part of the wheel
group. But the user that logs into this box needs to be.
Wondering if we want to transition the appliance to using the manageiq user or another one. I'd actually prefer admin rather than using manageiq but that may be introducing too many special accounts.
Maybe manageiq-admin
?
I like admin
The user will sudo
as root (or user manageiq
) to do most of their configuration
Thinking of just closing this for now.
This pull request has been automatically closed because it has not been updated for at least 3 months.
Feel free to reopen this pull request if these changes are still valid.
Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.
The new manageiq user needs access to the v2_key -- so when the key is created, the group is properly set.
This code is not fully tested. I need a little more work until I am able to build appliances on my local box and test the actual implementation of the kickstart, but this is what I typed on the command line.
To be honest, I'm not sure if the proper setup here is to chgrp the v2_key or to
chmod 2775
the directory to help others in the future with theirv2_key
endeavors.