-
Notifications
You must be signed in to change notification settings - Fork 130
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
fix: blackbox_exporter ansible-lint risky-octal #174
fix: blackbox_exporter ansible-lint risky-octal #174
Conversation
Signed-off-by: Thomas Venieris <thomas.venieris@gmail.com>
Same here, the github-actions bot labeling didn't trigger the blackbox_exporter roll checks. @tvenieris Do you know why these are not getting caught in CI? The ansible-lint pipeline should catch these. |
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## main #174 +/- ##
========================================
Coverage ? 100.00%
========================================
Files ? 2
Lines ? 34
Branches ? 2
========================================
Hits ? 34
Misses ? 0
Partials ? 0
Flags with carried forward coverage won't be shown. Click here to find out more. |
This needs a rebase. |
Signed-off-by: Thomas Venieris <thomas.venieris@gmail.com>
I don't think there's anything wrong with the CI. I am running ansible-lint at the top of the collection, inside the role or against a sample playbook and it just does not detect the risky-octal issue. So it's most likely an ansible-lint bug. The reason I am getting these errors is that I have embedded these roles into my own playbooks and there for reasons unknown the issue is detected. |
Just to show you how things look from my end, this is an ansible-lint run against the prometheus-community/ansible collection:
... and this is the octal-values issue getting detected in my own codebase:
|
Maybe if we included a test playbook at the top level. |
I tried that, it did not make a difference. I even tried to include a make-shift inventory, again with no success. |
Could it be the same issue as this? ansible/ansible-lint-action#172 |
@gardar I have never used ansible-lint-action just plain ansible-lint which I have installed using pip. Actually, I forgot to include the version in my last comment:
Therefore I doubt ansible/ansible-lint-action#172 is the root cause |
Can you please rebase? |
Signed-off-by: Thomas Venieris <thomas.venieris@gmail.com>
No description provided.