)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":22629,"name":"Michal Nasiadka","email":"mnasiadka@gmail.com","username":"mnasiadka"},"change_message_id":"6611d89e8326248a1702f1274c0deea70bbd081e","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"d2b3caf0_b84b29db","updated":"2023-12-19 06:57:05.000000000","message":"Can we also add the option to treat warnings as errors?","commit_id":"176aa5a42c3f03ece08fb87d8474c10551f0a384"},{"author":{"_account_id":32553,"name":"Sven Kieske","email":"sven_oss@posteo.de","username":"skieske"},"change_message_id":"2ecd6c827dcdadce8f9a6d59ac87306883729820","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"3802d719_d1b84803","updated":"2023-12-18 18:17:20.000000000","message":"tox -e linters produced previously:\n\n```\nWARNING  Listing 2 violation(s) that are fatal\nansible/roles/cinder/tasks/precheck.yml:58: jinja[spacing]: Jinja2 spacing could be improved: Cinder backup S3 backend is enabled, either the {{ item }} or {{ item | replace(\u0027cinder_backup_\u0027,\u0027\u0027) }} variable must be defined. -\u003e Cinder backup S3 backend is enabled, either the {{ item }} or {{ item | replace(\u0027cinder_backup_\u0027, \u0027\u0027) }} variable must be defined. (warning)\nansible/roles/glance/tasks/precheck.yml:28: jinja[spacing]: Jinja2 spacing could be improved: Glance S3 backend is enabled, either the {{ item }} or {{ item | replace(\u0027glance_backend_\u0027,\u0027\u0027) }} variable must be defined. -\u003e Glance S3 backend is enabled, either the {{ item }} or {{ item | replace(\u0027glance_backend_\u0027, \u0027\u0027) }} variable must be defined. (warning)\n\n              Rule Violation Summary               \n count tag            profile rule associated tags \n     2 jinja[spacing] basic   formatting (warning) \n```","commit_id":"176aa5a42c3f03ece08fb87d8474c10551f0a384"},{"author":{"_account_id":22629,"name":"Michal Nasiadka","email":"mnasiadka@gmail.com","username":"mnasiadka"},"change_message_id":"97ee150f8ba4c16bc86979e4bf533d8f8e394991","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7659399a_7bab7253","in_reply_to":"008c0c23_2d702008","updated":"2023-12-19 11:25:10.000000000","message":"Done","commit_id":"176aa5a42c3f03ece08fb87d8474c10551f0a384"},{"author":{"_account_id":22629,"name":"Michal Nasiadka","email":"mnasiadka@gmail.com","username":"mnasiadka"},"change_message_id":"38007fec1b6b151b3297588c100abf133e6ebc9e","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"008c0c23_2d702008","in_reply_to":"7c3177ed_5e3e3fcf","updated":"2023-12-19 10:36:30.000000000","message":"Seems there is:\n-s, --strict          Return non-zero exit code on warnings as well as errors\nhttps://ansible.readthedocs.io/projects/lint/usage/#using-commands","commit_id":"176aa5a42c3f03ece08fb87d8474c10551f0a384"},{"author":{"_account_id":32553,"name":"Sven Kieske","email":"sven_oss@posteo.de","username":"skieske"},"change_message_id":"3eac7cbb510dcf8faf9263eaba2710758e7f2d86","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7c3177ed_5e3e3fcf","in_reply_to":"d2b3caf0_b84b29db","updated":"2023-12-19 10:31:18.000000000","message":"well, if that feature existed, I would add that in a separate changeset.\n\nBut it seems, that ansible-lint doesn\u0027t provide such a feature. At least it\u0027s not builtin, see:\n\nhttps://github.com/ansible/ansible-lint/issues/236\n\nI see two options:\n\n1. raise this topic with upstream again, maybe they have changed there mind (some years have passed).\n2. hack it ourselves together, we already pass the `-p` switch to ansible-lint (--parseable). We could grep the output for warnings and then report an error (ansible-lints exit code is zero, even with warnings present).\n\nWhat do you think?","commit_id":"176aa5a42c3f03ece08fb87d8474c10551f0a384"}]}