Not possible to omit generating those messages, although you could say $ ansible-lint […] 2>/dev/null
If the positional argument were, say, a group_vars file and it was being linted as if it were a playbook, then "WARNING …" would clearly make sense. Or if you didn't intend "my_test.yml" to be linted as a playbook, then you'd be glad for the warning. As it is, since you can't pick which lintable schema to use on a given file (at least not from --help's output, or the missing man page), I'll stand by my original statement: it's an informational message that happens to begin with the text "WARNING". That's just my opinion, but ansible-lint is extremely opinionated after all. On Thursday, December 22, 2022 at 7:16:08 AM UTC-5 rajthecomputerguy wrote: > It is a warning , can you please tell me how to avoid this? > > *WARNING Overriding detected file kind 'yaml' with 'playbook' for given > positional argument: my_test.yml* > > On Thursday, December 22, 2022 at 5:22:50 PM UTC+5:30 [email protected] > wrote: > >> That isn't an error. It's just information: the yaml file is being >> treated as a playbook. >> >> On Thursday, December 22, 2022 at 5:40:02 AM UTC-5 rajthecomputerguy >> wrote: >> >>> Hi Team, >>> >>> I am facing below error while doing ansible-lint, Any help would be >>> appreciated >>> >>> command: *ansible-lint test.yaml* >>> >>> *Overriding detected file kind 'yaml' with 'playbook' for given >>> positional argument* >>> >>> Thanks, >>> Raj >>> >> -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/1cbbe42b-5756-4f11-8337-ef8d315a8250n%40googlegroups.com.
