-
Notifications
You must be signed in to change notification settings - Fork 4
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
[Bug] output_template not used #69
Comments
@montaropdf I just tested this locally and for me it works. It creates a new file
Is there any other option in the config.yaml? |
No this is the only option in the file. |
As a side note, I encounter the following issue while testing again with the template option in the configuration:
However, with |
Does the folder Can you do a |
I have performed further tests, the options However, with absolute path, I got the below error. |
This works for me.
This seems related somehow since its not finding the template. Can you answer these questions please?
|
I am using a Fedora 39 distribution on WSL. I don't run the tool inside a virtual environment I don't know if it could have an impact. |
WSL could be the problem here. Do you have the possibility to test it on a non-WSL system? In the meantime we'll try to reproduce it on WSL (I don't use Windows..) |
Same problem on a RedHat Enterprise Linux 9 machine with Python 3.9.18. |
Okay, I found the reason: |
With your fix, the |
Does your role have a |
Not all of them. |
In your output template you got this:
This part tries to include the defaults file. If it does not exist for a role, this will fail. Does this fail for roles where the defaults file exists? |
It fails when |
No, this works for me. I just tested it, even with an empty
|
When the file is called So in the end for this issue it was a stupid CKI problem. |
Regarding the use of templates.
I have created a configuration file with the following content:
And use it with the following command:
python -m aar_doc.cli --output-file someoutput.md --config-file=/path/to/configuration/file/config.yaml /path/to/role markdown
Unfortunately, the generated file has the same content as without the configuration file.
Originally posted by @montaropdf in #66 (comment)
The text was updated successfully, but these errors were encountered: