Possibly linux@lemmy.zip to linuxmemes@lemmy.worldEnglish · 11 months agoAnsible casually administering hundreds or thousands of deviceslemmy.zipimagemessage-square53fedilinkarrow-up1221arrow-down19
arrow-up1212arrow-down1imageAnsible casually administering hundreds or thousands of deviceslemmy.zipPossibly linux@lemmy.zip to linuxmemes@lemmy.worldEnglish · 11 months agomessage-square53fedilink
minus-squarertxn@lemmy.worldMlinkfedilinkEnglisharrow-up4·edit-211 months agoYou can use JSON to write the playbooks, then use a program like yq (which is a Yaml wrapper for jq) to convert it to Yaml. Something like cat playbook.json | yq --yaml-output > .temp_playbook.yml ansible-playbook .temp_playbook.yml
minus-squareMeanEYE@lemmy.worldlinkfedilinkarrow-up1·11 months agoI did not know that. That’s a useful one. Does it work the other way around?
minus-squarertxn@lemmy.worldMlinkfedilinkEnglisharrow-up2·11 months agoYes, both yq and jq are fantastic programs. yq can take either JSON or Yaml (or maybe others, I haven’t checked) as input, then it converts it to JSON before passing it to jq. yq outputs JSON by default, or Yaml if you pass it the --yaml-output option.
You can use JSON to write the playbooks, then use a program like
yq(which is a Yaml wrapper forjq) to convert it to Yaml. Something likeI did not know that. That’s a useful one. Does it work the other way around?
Yes, both
yqandjqare fantastic programs.yqcan take either JSON or Yaml (or maybe others, I haven’t checked) as input, then it converts it to JSON before passing it tojq.yqoutputs JSON by default, or Yaml if you pass it the--yaml-outputoption.