Skip to content
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

ansible-lint schema check fails for doc_changes with network collections #3261

Closed
KB-perByte opened this issue Apr 11, 2023 · 0 comments · Fixed by #3262
Closed

ansible-lint schema check fails for doc_changes with network collections #3261

KB-perByte opened this issue Apr 11, 2023 · 0 comments · Fixed by #3262
Labels

Comments

@KB-perByte
Copy link
Member

lint fails for doc_changes
valid section across Ansible network modules
https://github.com/ansible-collections/cisco.ios/blob/main/changelogs/config.yaml#L29

Summary
Issue Type
  • Bug Report
OS / ENVIRONMENT
ansible-lint --version
  • ansible installation method: one of source, pip, OS package
  • ansible-lint installation method: one of source, pip, OS package
STEPS TO REPRODUCE
Desired Behavior

Possible security bugs should be reported via email to security@ansible.com

Actual Behavior

Please give some details of what is happening.
Include a minimum complete verifiable example with:

  • minimized playbook to reproduce the error
  • the output of running ansible-lint including the command line used
  • if you're getting a stack trace, also the output of
    ansible-playbook --syntax-check playbook
WARNING  Listing 1 violation(s) that are fatal
schema[changelog]: Additional properties are not allowed ('doc_changes' was unexpected)
changelogs/changelog.yaml:1  Returned errors will not include exact line numbers, but they will mention
the schema name being used as a tag, like ``schema[playbook]``,
``schema[tasks]``.

This rule is not skippable and stops further processing of the file.

If incorrect schema was picked, you might want to either:

* move the file to standard location, so its file is detected correctly.
* use ``kinds:`` option in linter config to help it pick correct file type.


Error: Additional properties are not allowed ('doc_changes' was unexpected)
Read documentation for instructions on how to ignore specific rule violations.

                Rule Violation Summary                
 count tag               profile rule associated tags 
     1 schema[changelog] basic   core  
@KB-perByte KB-perByte added bug new Triage required labels Apr 11, 2023
@KB-perByte KB-perByte changed the title ansible-lint schema check fails for doc_changes for network collections ansible-lint schema check fails for doc_changes with network collections Apr 11, 2023
@ssbarnea ssbarnea removed the new Triage required label Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants