Replies: 1 comment
-
This is unrelated to vscode extension, see https://github.com/ansible-community/ansible-lint/blob/main/.ansible-lint#L76-L84 for how to override config. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Sanity check
redhat.ansible
extension is in use and the language of the document in this bug report shows up asAnsible
Summary
I have an Ansible project with one playbook (
deploy.yaml
) which imports a number of tasks from the same directory. Most of the time, this works well but there are a couple of task which will get this error:This appears to be due to the presence of a block comment at the top of the file. When my file starts like this, it will be treated as a playbook:
If I remove the comment block, it will be treated like the other tasks:
(In both cases, the file is picked up with the Ansible type)
I'm not sure whether this is directly the VSCode extension or the YAML server but it feels like there should at least be some documentation for how to override the guessed file types or a suggested project layout if there's a rigid assumption about where files live.
Extension version
v0.6.1
VS Code version
1.62.2
Ansible Version
OS / Environment
macOS
Relevant log output
No response
Beta Was this translation helpful? Give feedback.
All reactions