Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid "[Notice] Using configuration in /foo/bar/brakeman.yml" #300

Closed
mariozaizar opened this issue Mar 26, 2013 · 3 comments · Fixed by #306
Closed

Avoid "[Notice] Using configuration in /foo/bar/brakeman.yml" #300

mariozaizar opened this issue Mar 26, 2013 · 3 comments · Fixed by #306
Milestone

Comments

@mariozaizar
Copy link

Hi, hey thanks for brakeman it rocks!. I'm using it as part of my CI build script so, I try to keep simple the output, as you can see here:

Screen Shot 2013-03-26 at 9 24 49 AM

It was fine, until I decided to use a custom config file. Then I saw this notice [Notice] Using configuration in /foo/bar/brakeman.yml. I would like to avoid the notice message, or move it to the file. I've tried using pipes > /dev/null and 2>&1 but didn't work.

This is how I'm running the command:

bundle exec brakeman --quiet --summary --output tmp/brakeman.csv;
printf "Security .......................................................... ${green}✓ ${red}`cat tmp/brakeman.csv | grep Security | grep -v '(0)'` $reset";

Thanks a lot.

@presidentbeef
Copy link
Owner

Hi Mario,

Thanks for reporting this issue! It looks like you are using two features I didn't think anyone was using: CSV output and config files :)

The issue here is that the options are not actually set until the config file and the command line arguments are parsed. But the notification is prior to any of that, so --quiet doesn't work, even if specified in the config file. This should definitely be fixed.

However, everything except the report should go to STDERR, so a quick fix would be to run Brakeman like this:

brakeman 2> /dev/null

@mariozaizar
Copy link
Author

Cool, it works! Thanks!
Closing this.

@presidentbeef
Copy link
Owner

I'm going to re-open this to remind me to fix it ;)

@presidentbeef presidentbeef reopened this Mar 26, 2013
zlx added a commit to zlx/brakeman that referenced this issue May 2, 2013
Repository owner locked and limited conversation to collaborators Feb 16, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants