You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I detected a bug where antsibull-docs collection command will ignore a collection path configured inside ansible.cfg file. Apparently current logic implemented is to only recognize the environment variables overrides but fails to ask ansible about effective collection path used, ansible-config dump being the most effective way to report it (but even ansible --version would report it)
The issue is not critical as defining ANSIBLE_COLLECTIONS_PATH=... before calling the tool can be used as a workaround for forcing it to look elsewhere.
The text was updated successfully, but these errors were encountered:
antsibull-docs does not use ansible.cfg at all. That is a file used by ansible-core. So I don't see what ansible.cfg has to do with antsibull-docs.
Since you do not describe the situation in which you use antsibull-docs and encoutner this it is impossible to say anything about this, since the behavior of antsibull-docs varies greatly depending on the subcommand and the parameters passed.
I detected a bug where
antsibull-docs collection
command will ignore a collection path configured insideansible.cfg
file. Apparently current logic implemented is to only recognize the environment variables overrides but fails to ask ansible about effective collection path used,ansible-config dump
being the most effective way to report it (but evenansible --version
would report it)Based on my debugging the issue seems to be caused by
antsibull-docs/src/antsibull_docs/docs_parsing/__init__.py
Line 53 in f866406
The issue is not critical as defining
ANSIBLE_COLLECTIONS_PATH=...
before calling the tool can be used as a workaround for forcing it to look elsewhere.The text was updated successfully, but these errors were encountered: