SaltStack VS Ansible

Of course, booting from a disk is not the only option. If you want to automate installs across servers - you have to boot from the network. That is something you could play around with, in GNS3 for example, using FAI or your own system based on SaltStack. You could skip the installation altogether, and use a Live Image, or a Thin Client.

In the new style, when the tag is longer than 20 characters, an end of tag string is appended to the tag given by the string constant TAGEND, that is, two line feeds '\n\n'. When the tag is less than 20 characters then the tag is padded with pipes "|" out to 20 characters as before. When the tag is exactly 20 characters no padded is done. source: https://github.com/saltstack/salt/blob/master/salt/utils/event.py

https://github.com/saltstack/salt https://github.com/chocolatey/choco https://github.com/nextcloud https://github.com/authelia/authelia https://github.com/grafana/grafana

SaltStack

One thing that really irks me about Salt, though, is that they are very slow to fix bugs. My Salt states are littered with workarounds for bugs that have been open for multiple years. Even in basic things, like ssh authorized_keys management. Other than bug velocity, though, I've been pretty pleased with Salt.

Here are several related GitHub issues: - https://github.com/saltstack/salt/issues/54791 - https://github.com/saltstack/salt/issues/57541 - https://github.com/saltstack/salt/issues/16089

For clarity, here's the issue: https://github.com/saltstack/salt/issues/64111

Nightly builds on supported branches & master running the full test suite, producing fully tested builds. https://github.com/saltstack/salt/actions/workflows/nightly.yml

Also for systems administration and DevOps, I first used Ansible to streamline the management of our servers. Writing playbooks is OK, but going beyond that to convert them to roles is a good practice from collaboration perspective. This SDK approach worked quite well for me and my team. Now, I am developing NixOS modules for various services we deploy. In both cases, the goal is to compose well-defined and documented modules (SDK) into a complete system in a few lines of code (application).

Ansible,

You can use GitHub repos as RSS links and received notification about new releases. If you're using miniflux just past https://github.com/ansible/ansible/releases.atom

That said, I can't readily imagine why you couldn't do exactly what you said because the AnsibleModule[1] contract is JSON over stdin/stdout (and one can write Ansible modules in any programming language[2] - they just default to Python)

1: https://github.com/ansible/ansible/blob/v2.18.4/lib/ansible/...

2: https://docs.ansible.com/ansible-core/2.18/dev_guide/develop... and https://github.com/ansible/ansible/blob/v2.18.4/test/integra...

​​Ansible provides streamlined automation for IT orchestration and configuration management through its declarative language. Teams can efficiently define and execute automation tasks, ensuring consistent environment management. This tool provides simplicity and effectiveness making it a valuable tool for managing complex IT infrastructures at scale.

A key aspect of this starter kit is its comprehensive automation using Ansible. The polaris-forge-setup directory houses Ansible playbooks that:

Hi, in this post, we will use Libvirt with Terraform to provision 2 KVM locally and after that, we will Deploy Flask App & PostgreSQL using Ansible.

Ansible GitHub Repository

Ansible is an open-source tool that excels in infrastructure configuration. With an agentless architecture (no services need to be installed on the managed machines), it communicates with machines over SSH.