this post was submitted on 26 Jan 2024
197 points (95.8% liked)

linuxmemes

21192 readers
151 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    197
    Ansible casually administering hundreds or thousands of devices (lemmy.zip)
    submitted 9 months ago by possiblylinux127@lemmy.zip to c/linuxmemes@lemmy.world
    50 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] rtxn@lemmy.world 7 points 9 months ago* (last edited 9 months ago) (1 children)

    I don't particularly like yaml as a data storage language because of its use of significant whitespaces, but for the minimal complexity of my own playbooks, I don't mind it.

    What would you consider to be an ideal language for playbooks?

    [–] MeanEYE@lemmy.world 2 points 9 months ago (1 children)

    Am not sure to be honest. I always liked JSON even though it's very rigid. Even so, most of software I write stores config in JSON simply because it's easy to parse and it's supported by literally everything. It's also pretty minimalist.

    Perhaps something more strict and defined would be better. I think I'd even prefer XML to YAML.

    [–] rtxn@lemmy.world 3 points 9 months ago* (last edited 9 months ago) (1 children)

    You 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
    [–] MeanEYE@lemmy.world 1 points 9 months ago (1 children)

    I did not know that. That's a useful one. Does it work the other way around?

    [–] rtxn@lemmy.world 2 points 9 months ago

    Yes, 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.