{"action":"closed","issue":{"url":"https://api.github.com/repos/zaproxy/zaproxy/issues/4824","repository_url":"https://api.github.com/repos/zaproxy/zaproxy","labels_url":"https://api.github.com/repos/zaproxy/zaproxy/issues/4824/labels{/name}","comments_url":"https://api.github.com/repos/zaproxy/zaproxy/issues/4824/comments","events_url":"https://api.github.com/repos/zaproxy/zaproxy/issues/4824/events","html_url":"https://github.com/zaproxy/zaproxy/issues/4824","id":339273386,"node_id":"MDU6SXNzdWUzMzkyNzMzODY=","number":4824,"title":"zap-baseline should have option to not fail on warnings (optionally)","user":{"login":"michaelneale","id":14976,"node_id":"MDQ6VXNlcjE0OTc2","avatar_url":"https://avatars0.githubusercontent.com/u/14976?v=4","gravatar_id":"","url":"https://api.github.com/users/michaelneale","html_url":"https://github.com/michaelneale","followers_url":"https://api.github.com/users/michaelneale/followers","following_url":"https://api.github.com/users/michaelneale/following{/other_user}","gists_url":"https://api.github.com/users/michaelneale/gists{/gist_id}","starred_url":"https://api.github.com/users/michaelneale/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/michaelneale/subscriptions","organizations_url":"https://api.github.com/users/michaelneale/orgs","repos_url":"https://api.github.com/users/michaelneale/repos","events_url":"https://api.github.com/users/michaelneale/events{/privacy}","received_events_url":"https://api.github.com/users/michaelneale/received_events","type":"User","site_admin":false},"labels":[{"id":678291375,"node_id":"MDU6TGFiZWw2NzgyOTEzNzU=","url":"https://api.github.com/repos/zaproxy/zaproxy/labels/Docker","name":"Docker","color":"8B4513","default":false},{"id":220421415,"node_id":"MDU6TGFiZWwyMjA0MjE0MTU=","url":"https://api.github.com/repos/zaproxy/zaproxy/labels/Usability","name":"Usability","color":"ededed","default":false},{"id":220063776,"node_id":"MDU6TGFiZWwyMjAwNjM3NzY=","url":"https://api.github.com/repos/zaproxy/zaproxy/labels/enhancement","name":"enhancement","color":"84b6eb","default":true}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-07-09T00:46:37Z","updated_at":"2018-07-09T10:02:55Z","closed_at":"2018-07-09T10:02:55Z","author_association":"NONE","body":"**Is your feature request related to a problem? Please describe.**\r\nWhen using the most excellent zap-baseline.py from the Docker image as part of a build pipeline, it returns a non zero code for warnings. The return code is distinct for failures vs warnings.\r\n\r\nThis causes build pipelines to generally fail - as the convention of non zero meaning \"all is not ok\" is used (and with build pipelines - it is mostly all or nothing, pass/fail). \r\n\r\n\r\n**Describe the solution you'd like**\r\nI have a pull request open ( https://github.com/zaproxy/zaproxy/pull/4825 ) that ads in an option to ignore warnings (they are still logged, they just don't change the response code). \r\n\r\n**Describe alternatives you've considered**\r\nI thought maybe warnings could be upgraded to return a failure (if they are a problem) but clearly they are warnings for a reason!\r\nAlso did consider build pipelines that take the response code and specifically ignore the warning return code (but that seems a little hack-ish). \r\n\r\n**Additional context**\r\nRelevant when using the docker image as part of a build pipeline. \r\n"}}
{"actor":{"display_login":"thc202"}}