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
Sometimes you just want to quickly run a playbook pointing to z/OS and don't really want to create all the group_vars, host_vars , although using group_vars and host_vars is recommend because it makes your projects portable. So how do you do put environment vars for z/OS in your playbook? See the below example.
You will need to edit variable ZOAU and PYZ to correspond to your installation.
This is how it should look if you want to use environment vars in your playbook as opposed to using group_vars and host_vars.
For ZOAU version 1.3.0 or later, you must set the PYZ_VERSION, for versions older than 1.3.0, you can set it to an empty string, eg PYZ_VERSION="".
DocumentationReport documetation errors or needed changes
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Sometimes you just want to quickly run a playbook pointing to z/OS and don't really want to create all the
group_vars
,host_vars
, although usinggroup_vars
andhost_vars
is recommend because it makes your projects portable. So how do you do put environment vars for z/OS in your playbook? See the below example.You will need to edit variable
ZOAU
andPYZ
to correspond to your installation.This is how it should look if you want to use environment vars in your playbook as opposed to using
group_vars
andhost_vars
.For ZOAU version 1.3.0 or later, you must set the PYZ_VERSION, for versions older than 1.3.0, you can set it to an empty string, eg
PYZ_VERSION=""
.Beta Was this translation helpful? Give feedback.
All reactions