This looks pretty cool, wish I had heard of it at my last job, where we orchestrated all of our physical servers using Salt.

There are times when unfortunately the end result can be a bit tricky to predict, especially when using the reactor system.

These days all the cool kids use k8s, but I think most often it's overkill and Salt works extremely well for traditional (non microservice) setups. It's especially useful if you have a mix of physical servers and VMs.

Can someone give me a TLRD on salt, is it something like Ansible but for InfoSec?

TL;DR: Salt is complex, multi-purpose tool, with event-driven orchestration and remote execution engine capabilities. In other words, it implicitly does what Ansible can do, plus many other things. What I personally like the most is the ease to develop and extend features, vs., e.g., a clogged DSL as many popular tools (unfortunately) impose.

I was under the impression it was a direct competitor to the likes of Ansible, Chef, etc. (all differ in their approaches but it's effectively the same problem space)

Unaware of a specific infosec slant.

It's Ansible, plus the total lack of noticing when you've gone too far inventing cutesy nicknames totally devoid of any meaningful connection to the concept they are supposedly describing.

Then you probably shouldn't look at the uWSGI documentation.

"The emperor-tyrant forced my master to commit harakiri."

Salt, has extensive infosec portfolio. Some cool stuff. Look at their site..they seem to have pushed into secops

Really great