-
Notifications
You must be signed in to change notification settings - Fork 666
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 is ignoring meta/main.yaml instead of meta/main.yml #3849
Comments
Too bad I did not check the issue tracker carefully. Would have easily saved me two to three hours 🤦 Had to figure it out for myself. Also it is not just |
Yes, that is inconsistent with the rest of ansible. |
This issue is addressed in Support meta main yaml extension |
Do |
Both Though I suspect that my earlier comment was more about not supporting the |
Issue Type
Molecule and Ansible details
Molecule installation method (one of):
Ansible installation method (one of):
Detail any linters or test runners used:
Desired Behavior
Either inform the user about the missing
meta/main.yml
or check formeta/main.yaml
too and when it's not there report that, when necessary. But ansible-lint is absolutly fine with *.yaml files, so it should be accepted by molecule too.Actual Behaviour
Whyever I did, but some time ago, I'm renamed a
meta/main.yml
tometa/main.yaml
. Today I wanted to add molecule tests to my roles and it always ended with:The reason was - molecule did not know the name of the role inside the repo, because it looks silently for meta/main.yml and ignores the missing file or does not provide any feetback that it could not find a meta/main-file.
When I rename meta/main.yaml to ...yml, its working
The text was updated successfully, but these errors were encountered: