-
Notifications
You must be signed in to change notification settings - Fork 10
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
Added lint to molecule #161
Conversation
Since the code fails lint the addition of lint tests in molecule will fail. Fixing the faults or explicitly disabling them in the code will make this PR work and keep future molecule tests fail if the code fails lint. |
@staticdev Now fixed all lint warnings in the code. Looks like there is somethiing in the CI/CD chain in github that makes it fail anyway. Any ideas? |
Change-Id: I537aa1a622a8dc0a85b181f14c3eb709df8d8477
Change-Id: Iea66c5aaf7d2383743db7828c68218db4d511592
Hi @staticdev , Lint then need to be added in the test.yml file (I can do this). Would you like this or to remove lint from being run default every time one builds with molecule? I would prefer it being run every time one run molecule but it is your repository. |
molecule/default/molecule.yml
Outdated
@@ -13,3 +13,7 @@ platforms: | |||
pre_build_image: true | |||
provisioner: | |||
name: ansible |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are the advantages of having it on molecule in this case? I added a separate lint workflow because with molecule the same checks were repeated in each distro for molecule, resulting in longer wait in Github Actions. Am I missing something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@staticdev the benefit would be that one would always run the linting everyting one run molecule during development on the local computer and could fix lint issues as soon as they occur whithout needing the extra step of running lint explicitly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MorganLindqvist I understand your point but for me does not justify the time on pipeline. With precommit I forget about lint and focus on my change while developing, then I worry when I do the commits. Also for me is bad to change one role to lint different since I have a standard already for many roles. Hope you can also see my side since I have extra costs involved to maintain the role.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@staticdev sure, will remove lint from the molecule build
Change-Id: Id077e0d93808bb7fbc9185f9e55061b15d563cf2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot @MorganLindqvist ! LGTM.
Added so that the lint test is always run when using molecule
Change-Id: I537aa1a622a8dc0a85b181f14c3eb709df8d8477