While some variables are necessary to configure based on target systems, eg: PATH, LIBPATH, PYTHONPATH based on where dependencies are located and installed on target systems, other variables have fairly consistent values across all z/OS systems:
This epic tracks the effort to change the community code such that certain environment variable values are pre-configured for the z/OS Ansible user "out-of-the-box".
Notice in the Ansible community src code - connection dir, there exist provisions for Windows OS (winrm and psrp) as well as for Python shell (paramiko). There may be a way to include customization for z/OS targets.
Currently, an Ansible user must set about 10 environment variables in order to target a z/OS managed node.
While some variables are necessary to configure based on target systems, eg:
PATH
,LIBPATH
,PYTHONPATH
based on where dependencies are located and installed on target systems, other variables have fairly consistent values across all z/OS systems:This epic tracks the effort to change the community code such that certain environment variable values are pre-configured for the z/OS Ansible user "out-of-the-box".
Notice in the Ansible community src code - connection dir, there exist provisions for Windows OS (
winrm
andpsrp
) as well as for Python shell (paramiko
). There may be a way to include customization for z/OS targets.For additional context:
1221
The items in this epic:
1221
1433
1434
1435
1436
1437