Its not uncommon to ask for a standard set of information from a user of the ibm_zos_core collection, it might be good if we could come up with hassle free way to ask for the output of what we generally need.
One idea would be a playbook be included with the collection, we generally don't include playbooks because of maintenance and put them in a samples repository but one like this may not undergo change that would make it suitable to include in the collection.
Ideas of content to collect:
ansible version (`ansible –version`)
ibm_zos_core version ( ` ansible-galaxy collection list |grep 'ibm_zos_core' ` or follow [link](https://ibm.github.io/z_ansible_collections_doc/faqs/faqs.html#how-can-i-know-which-version-of-a-collection-i-am-using))
Python version on controller (`python –version`)
IBM Enterprise Python version on z/OS managed node
ZOAU version used on the z/OS managed node
We could even get more advanced and take the playbook name as an arg and wrap this around it:
Playbook execution with verbose, if running from AAP , ensure DEBUG highest level is set, if running addhoc `ANSIBLE_DEBUG=1 ansible-playbook -i inventory your-playbook.yml -vvvv`
Is there an existing issue for this?
Ansible module
No response
Enabler description
Its not uncommon to ask for a standard set of information from a user of the ibm_zos_core collection, it might be good if we could come up with hassle free way to ask for the output of what we generally need.
One idea would be a playbook be included with the collection, we generally don't include playbooks because of maintenance and put them in a samples repository but one like this may not undergo change that would make it suitable to include in the collection.
Ideas of content to collect:
We could even get more advanced and take the playbook name as an arg and wrap this around it:
Optionally we could write it all to a file.