+1, i'd support this as the 2 commits in there are not in the normal/runtime flow for oslo.policy and just touch the doc bits. Thanks, Dims On Tue, Aug 1, 2017 at 4:36 PM, Lance Bragstad <lbragstad at gmail.com> wrote: > I was cleaning up a few documentation things for keystone and noticed an > issue with how the configuration reference was rendering. It turns out > the oslo.policy library needed a few tweaks to the show-policy directive > along with some changes to keystone that allowed us to properly render > all default policies. I documented these in a bug report tagging both > projects [0]. > > Two fixes were made to the oslo.policy library (thanks, Doug!) that will > allow projects to render their entire policy document using the > show-policy directive. Both fixes have merged in oslo.policy master and > have been backported to stable/pike. I also have a release proposed to > cut a new version of oslo.policy for us to use for pike [1]. > > Opening this up for discussion to see if we can grant an FFE so that we > can use the proper version of oslo.policy. More context in IRC as well [2]. > > Let me know if you have any questions. Thanks! > > Lance > > [0] https://bugs.launchpad.net/keystone/+bug/1707246 > [1] https://review.openstack.org/#/c/489599/ > [2] > http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-release.2017-08-01.log.html#t2017-08-01T18:14:57 > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Davanum Srinivas :: https://twitter.com/dims