search

ansible / ansible-content-parser

Apache License 2.0
3 stars 4 forks source link

Change output file extension from .json to .jsonl and specify ANSIBLE_LINT_NODEPS envvar #34

Closed TamiTakamiya closed 9 months ago

TamiTakamiya commented 9 months ago

Issue: https://issues.redhat.com/browse/AAP-19303

Description

Address areas of improvements on Ansible Content Parser found in the Jan 8 walk-through:

  1. File extension of the output. The postprocess code provided by IBM expects the training data to have the .jsonl extension while the current version of Ansible Content Parser genertes ftdata.json. We should change Ansible Content Parser to generate ftdata.jsonl.
  2. The latest ansible-lint supports the environment variable ANSIBLE_LINT_NODEPS to ignore dependency errors, which can occur in content parser processing. Ansible Content Parser should set the variable.

Testing

Unit tests are included.

Steps to test

  1. Build the Content Parser following the instructions
  2. Run ansible-content-parser against Ansible code repositories to make sure if no function are broken.

Scenarios tested

ansible-content-parser could generate ftdata.jsonl file from the ansible-examples repo.