You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rather than passing in a callable path for custom MKPs and using NOP post processing, I think what would be better is to implement a discoverable plugin structure that will guide implementers to define an entry point function that returns a MKP callable and optional post-processing callable.
mattsb42-aws
changed the title
investigate converting to discoverable plugin structure for MKP/post-processing
convert master key discovery to use setuptools entry points
Oct 15, 2017
mattsb42-aws
changed the title
convert master key discovery to use setuptools entry points
convert master key provider discovery to use setuptools entry points
Oct 15, 2017
Rather than passing in a callable path for custom MKPs and using NOP post processing, I think what would be better is to implement a discoverable plugin structure that will guide implementers to define an entry point function that returns a MKP callable and optional post-processing callable.
https://packaging.python.org/guides/creating-and-discovering-plugins/
http://setuptools.readthedocs.io/en/latest/setuptools.html#dynamic-discovery-of-services-and-plugins
The text was updated successfully, but these errors were encountered: