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
ansible --version 2> /dev/null | head -n 1 >${AWX_ISOLATED_DATA_DIR}/ansible_version.txt
that included files
collections.json
ansible_version.txt
which were produced by the obvious commands. This data was consumed by AWX, saved to the database, and passed along to analytics.
Implementation details are TBD, of course. However, I would suggest that we could reasonably pass this data in the status_callback for the starting status, and it is fully expected that this would have to be intentionally enabled by the caller (just as the AWX_ISOLATED_DATA_DIR env var was abused before), so whatever instructions for adding this data will then subsequently be added by AWX.
To clarify (about the format of delivery) - we don't need a file named collections.json. We just need the data somewhere and instructions so that we can collect it in AWX. This is why I propose the status_handler, as that could be passed in a dictionary that is already being passed from the worker to the processor, and AWX could just read that inside of an existing callback method.
The text was updated successfully, but these errors were encountered:
We need an updated alternative for getting the data which was previously produced in the entrypoint here:
ansible-runner/utils/entrypoint.sh
Lines 70 to 73 in c311e81
that included files
collections.json
ansible_version.txt
which were produced by the obvious commands. This data was consumed by AWX, saved to the database, and passed along to analytics.
Implementation details are TBD, of course. However, I would suggest that we could reasonably pass this data in the status_callback for the starting status, and it is fully expected that this would have to be intentionally enabled by the caller (just as the
AWX_ISOLATED_DATA_DIR
env var was abused before), so whatever instructions for adding this data will then subsequently be added by AWX.To clarify (about the format of delivery) - we don't need a file named
collections.json
. We just need the data somewhere and instructions so that we can collect it in AWX. This is why I propose the status_handler, as that could be passed in a dictionary that is already being passed from the worker to the processor, and AWX could just read that inside of an existing callback method.The text was updated successfully, but these errors were encountered: