-
Notifications
You must be signed in to change notification settings - Fork 656
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
'molecule init' doesn't comply with documented 'molecule lint' configuration #3481
Labels
Comments
ziegenberg
added a commit
to ziegenberg/molecule
that referenced
this issue
Apr 11, 2022
Fixes: ansible#3481 Signed-off-by: Daniel Ziegenberg <daniel@ziegenberg.at>
ssbarnea
pushed a commit
that referenced
this issue
Apr 12, 2022
Fixes: #3481 Signed-off-by: Daniel Ziegenberg <daniel@ziegenberg.at>
muellerbe
added a commit
to muellerbe/molecule
that referenced
this issue
Oct 12, 2022
zhan9san
pushed a commit
that referenced
this issue
Oct 13, 2022
davedittrich
pushed a commit
to davedittrich/molecule
that referenced
this issue
Oct 24, 2022
muellerbe
pushed a commit
to muellerbe/molecule
that referenced
this issue
Nov 24, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Type
Molecule and Ansible details
Molecule installation method:
Ansible installation method:
Detail any linters or test runners used:
Desired Behavior
When creating a new role I would expect molecule to create a consistent skeleton for itself that complies with FQCN at the very least. This is because, as stated by doc:
So as of today, I'm expecting it to support these (if I'm mistaken here I'd suggest a more clear specification in the doc):
After applying as suggested about linting by the https://github.com/ansible-community/molecule/blob/v3.6.1/docs/configuration.rst#lint and populating proper info to
meta/main.yml
linter shouldn't complain at all, like:Actual Behaviour
molecule lint
also checksmolecule
directory, generating these errors:destroy.yml
fileSteps to reproduce:
The text was updated successfully, but these errors were encountered: