On Tue, Aug 01, 2017 at 06:32:36PM -0500, Matthew Thode wrote:
> +1 here as well, my only concern is that this will need to be consumed
> by so many projects. If the community consensus on this is to go
> foraward with it then it's OK then.
>
>
+1 here as well, my only concern is that this will need to be consumed
by so many projects. If the community consensus on this is to go
foraward with it then it's OK then.
http://codesearch.openstack.org/?q=oslo.policy=nope=requirements.txt=
On 17-08-01 16:58:53, Doug Hellmann wrote:
> Excerpts
Excerpts from Davanum Srinivas (dims)'s message of 2017-08-01 16:38:13 -0400:
> +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.
+1 as well
>
> Thanks,
> Dims
>
> On Tue, Aug 1, 2017 at 4:36 PM, Lance Bragstad
>
> 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
+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 wrote:
> I was cleaning up a few documentation things for keystone and noticed an
>
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