Customer use case is as a hosting provider requires control access and permission within the stack in a granular fashion. The way that this is done (presently) is through the use of each component's policy.json file. The ability to automate this via puppet or heat template at time of deploy would be a nice feature to have as it would assist in consolidating the post deployment actions that are being done and allow for a structured approach in crafting specialized permissions. ==== Additional info Due to the nature of hosting, this customer would like to have the ability to dictate during the initial data dump into director to add the configuration changes to each components policy.json file. This would allow for the services to be hardened at the time of deployment rather than either being scripted out later or a manual process post deploy.
*** Bug 1304024 has been marked as a duplicate of this bug. ***
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
The blueprint has been created upstream:https://blueprints.launchpad.net/tripleo/+spec/modify-policy-json Target is pike-1 milestone for now.
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
Verified on build 2017-11-20.1. Update scenario verified on 2017-11-20.1 -> 2017-11.22.7
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462