Keep it simple
-
[email protected]replied to [email protected] last edited by
Only 1.1. Which everybody has been fiercely clinging onto since 2009, because YAML 1.2 did not seem to consider it a problem that they broke backwards compatibility on that behavior. So now the only way to keep existing YAML files working is for us all to keep pretending YAML 1.2 does not exist.
-
[email protected]replied to [email protected] last edited by
I feel I spend more time iterating yaml.
There isn't any tooling that actually helps you write it.I feel like there is a gap in the market for a solution that uses typescript, typed python or some other type-able scripting language, which then generates the yaml files.
A language that has language servers, intellisense, all the modern dev tools. Schemas are provided as simple type descriptors. And whatever script you write then produces the correct result.
Some sort of framework on top of that to provide an opinionated workflow, and some tooling to lint/validate/produce.
And the result is yaml files which can be checked/diffed against in-place config, and version controlled for consistency. -
[email protected]replied to [email protected] last edited by
XML is extremely verbose.
Again, requires some other tooling to generate (I feel I can point to JavaScript for an example of XML manipulation) -
Jist wait until you have to start fucking around with multiple incompatible versions of python for different targets.
-
[email protected]replied to [email protected] last edited by
Hello? Its me, NixOS.
-
Because group or host vars are hard?
-
[email protected]replied to [email protected] last edited by
That's what ansible-lint is for.
-
[email protected]replied to [email protected] last edited by
Reminds me of AutoHotkey
-
[email protected]replied to [email protected] last edited by
You mean like ansible-lint or yaml-lint?
-
[email protected]replied to [email protected] last edited by
Wtf is SSH and why should I care?
-
[email protected]replied to [email protected] last edited by
SSH is a network protocol for making secure connections, allowing remote access to various systems. As for why you should care, if you didn't know what SSH was, then you probably shouldn't care since you aren't the target audience. It's fringe knowledge for me too.
-
[email protected]replied to [email protected] last edited by
Are you looking for an editor that can format YAML out-of-the-box or with plugins? In my experience, most editors only support a small number of formats out of the box and extend that functionality with plugins. I have yet to find a solid, production editor without a decent YAML formatter. If you’re using one of the common commercial ones, Red Hat maintains many that work explicitly for Ansible.
-
[email protected]replied to [email protected] last edited by
I mean sure or you could just start by using a format that's not so painfully strict with how it's laid out. I miss the good old INI config. It couldn't give two shits how you format it, throw in random spaces random tabs random new lines so long as the value was correct
-
[email protected]replied to [email protected] last edited by
I hate ini. Lists stuck in ini.
-
NixOS : no dudes, its now raw warbling madness, its great. Just great. So easy. Please read these 17 guides that are outdated every minute to get started.
Ive tried to start using NixOS 3 times now, and it hasent took. Link me an actually good beginner guide and I might believe you.
-
Listen. The more painful it is up front, the better you'll feel once you get it.
NixOS & Flakes Book | Home Page
An unofficial and opinionated book for beginners
NixOS & Flakes Book (nixos-and-flakes.thiscute.world)
-
[email protected]replied to [email protected] last edited by
Honestly, fuck Ansible.
It's the dialup of automation tools. It was probably amazing 10 years ago.
It's YAML is awful, it scales terribly, it's so fucking slow at literally everything, it gives people who have no clue what they're doing a false sense of confidence.
The number of times I've seen app teams waste the time of support groups and engineers because something went wrong and they didn't have the knowledge to know why and need to waste so many man hours having other people solve it for them. I (the engineer) was added to a chat that had 15 people in it because they, after running ansible, saw errors in their server... So clearly there was a problem with the server... At no point did they question there Ansible job.
Of the various tools I've used, I prefer Salt. The YAML is slightly less ass and it's so much faster while also seeming to scaling better too. It by no means is perfect.
-
Thanks for including an alternative you'd recommend!
-
AHK grammar is a fucking mess, honestly.
-
Ahh, I didn't realize we had mixed some "git gud" dark souls shit into my devops.
But seriously, I'll give your guide a look. Everyone should taste madness occasionally.