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
{{ message }}
This repository has been archived by the owner on Jun 10, 2024. It is now read-only.
The blurb in the issue boilerplate for request 'ansible --version' output is super useful.
Adding some support for the next step could improve bug reports even more.
for ex ansible-playbook --issue-info site.yml
'--issue-info' could include:
all the 'ansible --version' info
any non-default config
controller env info (os, arch, python version, etc)
what inventory mechanism was used
what roles were referenced
module/library paths and versions
what modules/tasks were referenced
what module/tasks were actually invoked
Basically, enough info to figure out the specific folks to ping about the issue (and/or assign, etc).
Stretch goal:
Implement so it dumps the info a format that could be 'replayed' to some degree.
(for ex, checkout the matching version, setup matching config, matching python version, roles versions, etc).
The text was updated successfully, but these errors were encountered:
The blurb in the issue boilerplate for request 'ansible --version' output is super useful.
Adding some support for the next step could improve bug reports even more.
for ex
ansible-playbook --issue-info site.yml
'--issue-info' could include:
Basically, enough info to figure out the specific folks to ping about the issue (and/or assign, etc).
Stretch goal:
Implement so it dumps the info a format that could be 'replayed' to some degree.
(for ex, checkout the matching version, setup matching config, matching python version, roles versions, etc).
The text was updated successfully, but these errors were encountered: