Bug 1475252 - [RFE] Document the minimal permissions required to run bootstrap.py
[RFE] Document the minimal permissions required to run bootstrap.py
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Docs Host Configuration Guide (Show other bugs)
Unspecified Unspecified
medium Severity medium (vote)
: GA
: 6.X
Assigned To: Charles Wood
Russell Dickenson
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2017-07-26 05:45 EDT by Rich Jerrido
Modified: 2017-08-18 04:41 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-08-17 06:04:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rich Jerrido 2017-07-26 05:45:47 EDT
In the host-configuration guide (section 10.5), please add a section on the minimum permissions required to run the bootstrap script. Upstream docs here (https://github.com/Katello/katello-client-bootstrap/blob/master/README.md) in the 'Permissions' section. 

Additionally to create a role for a user with the minimal permissions to run bootstrap.py a user can use hammer to generate this: 

hammer role create --name "$ROLE"
hammer filter create --role "$ROLE" --permissions view_organizations
hammer filter create --role "$ROLE" --permissions view_locations
hammer filter create --role "$ROLE" --permissions view_domains
hammer filter create --role "$ROLE" --permissions view_hostgroups
hammer filter create --role "$ROLE" --permissions view_hosts
hammer filter create --role "$ROLE" --permissions view_architectures
hammer filter create --role "$ROLE" --permissions view_ptables
hammer filter create --role "$ROLE" --permissions view_operatingsystems
hammer filter create --role "$ROLE" --permissions create_hosts
Comment 1 Andrew Dahms 2017-08-01 21:26:22 EDT
Assigning to Charles for review.
Comment 12 Charles Wood 2017-08-17 06:04:15 EDT
The content has now been committed to 6.3 master branch ready for the next release.

Note You need to log in before you can comment on or make changes to this bug.