-
Notifications
You must be signed in to change notification settings - Fork 30
Fix linter #43
Fix linter #43
Conversation
Ok, now the "lint" step passes. ERROR! couldn't resolve module/action 'community.docker.docker_container'. This often indicates a misspelling, missing collection, or incorrect module path. The issue may be explained here: ansible/molecule#2755 Either we try to fix the molecule//collections.yml for 2.9 and 2.10. Or we could skip those versions to use ansible 3.1, 4.7 and 5.4 that are out for a while now. But for people still on Ansible Automation Platform 1, the supported version is the 2.9... |
This solutions is copied from ansible/molecule#2755 (comment)
Ok, now it works up utile this: TASK [ansible-mysqld_exporter : Ensure mysqld_exporter is enabled on boot] ***** But I may have fixed that in PR #40 |
Mergify now says: The new Mergify configuration is valid I learned a lot about CircleCI and Github, thanks for that :) Is there somebody at cloudalchemy who can find the time to review the PR please? @paulfantom maybe? |
We have a bunch of things to fix in our CI right now. The changes are mostly done in our skeleton/automated updates. But we need to get things pushed out to all of the other projects. I'm planning to do a bit of a hackathon with @paulfantom sometime soon to get things cleaned up. |
Thanks for the reply @SuperQ |
I've removed the dot after the command 'ansible-lint' because that seems to make it fails to find the yaml files. Then I had to fix the role path in molecule and a linting problem in prepare.yml I felt guilty to have PR a non-functional ansible-lint configuration even if you said you're working on your CI. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Not stale |
This role has been deprecated in favor of a the prometheus-community/ansible collection. |
This is an attempt to fix #42