Hi Ryan,
Keeping in mind that 'mistral-lib' must not depend on ‘mistral’ below are my
comments:
I think porting keystone utils over to mistral-lib is OK, I don’t see any other
options (‘mistral’ will depend on ‘mistral-lib’ but not the way around)
Porting the entire mistral.context is OK too for
In accordance with the spec[1], I started a patch[2] to port security
related items from mistral to mistral-lib. This may not be the right way
to approach this task and I'm hoping the patch provides a means to
illustrate the problem and starts a discussion on the right solution.
A custom action t
