Hi Cyril, This is a really cool idea. It should be fairly easy to implement and can only help make Bandit more usable. To be honest enhancing the way we're using the 'bandit.yaml' file has been on our list for a while.
A tool like this seems like it would be a nice intermediate solution until we get a better config file approach. I'd like for it to live in the Bandit repo. The best way forward is probably to create a quick blueprint to track the work and whoever wants to take it forward can assign it to themselves. By the way, it's really cool to see Oslo using Bandit! Thanks, -Travis On Mon, Nov 2, 2015 at 1:22 PM, Cyril Roelandt <cy...@redhat.com> wrote: >Whenever a new version of bandit comes out, one can grab the latest >config file example from the bandit release, and re-run the above >command. The generated config file will include all the new checkers. > >What do you think? Could this be a useful tool to handle bandit >configurations?
smime.p7s
Description: S/MIME cryptographic signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
