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

Starting with ansible-lint 5.0.x format of output changed #34

Closed
chrisrohr opened this issue Jul 24, 2021 · 3 comments · Fixed by #35
Closed

Starting with ansible-lint 5.0.x format of output changed #34

chrisrohr opened this issue Jul 24, 2021 · 3 comments · Fixed by #35
Milestone

Comments

@chrisrohr
Copy link

Hey there,

I wanted to add a ticket here as I noticed that starting with this commit (ansible/ansible-lint#1305) on ansible-lint, they removed the E### rule id and replaced them all with text based ids. This will obviously break the link to sonar. If someone could point me in the right direction, I could try to provide a PR to address this.

This will probably be a little bit harder to stay backwards compatible like you did with the ANSIBLE##### to E### transition so not sure if you would want this as a breaking change or not.

@sbaudoin
Copy link
Owner

Hello,

Thanks for reporting the issue. I'll have a look a this.

@sbaudoin sbaudoin mentioned this issue Jul 25, 2021
@sbaudoin sbaudoin added this to the 2.5.0 milestone Jul 25, 2021
@sbaudoin
Copy link
Owner

ansible-lint keeps on changing the output format, this is really a pain: 5.0.0 to 5.0.2 had the "new" syntax "error_id file:line", but starting from 5.0.3 this is the old syntax "file:line: error_id"...

Anyway, adding the new rules should be sufficient to fix the problem.

@chrisrohr
Copy link
Author

Thank you for checking on this. Please let me know if you want me to try to submit a PR for it.

@sbaudoin sbaudoin mentioned this issue Aug 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants