#saltstack
do you have alternatives to Ansible or Saltstack?
November 19, 2026 at 11:48 AM
…I'd gotten bitten by the vagaries of YAML's `>-` a few times in the past — in both Ansible and SaltStack — but this was Terraform. I'd been conscerned that I'd run into vagaries of a Go-based implementation of the YAML parser, but, nope. Everything worked.
November 19, 2026 at 4:50 PM
I'm very much an ansible user. I used to be big on saltstack, but I kept getting frustrated with their coding. Chef and Puppet I believe both use ruby (on rails?). I finally settled with ansible as being easier than doing custom scripts and no agent to deal with.
November 19, 2026 at 1:09 PM
Salt autosign_grains.conf pins minion key acceptance to allowed grain values via a Python runner. Enforce it on 3005+ across Ubuntu, Debian, and RHEL. #saltstack #security #ValtersIT https://www.valtersit.com/vault/enforce-salt-master-autoaccept-with-fingerprint-pinning-via--11c535/
Enforce Salt Master Auto-Accept with Fingerprint Pinning via Autosign Grains
www.valtersit.com
November 11, 2026 at 2:50 PM
If you're interested in bars I can recommend a few. Used to spend a bit of time in downtown SLC during the SaltStack days. One that's a fun place to hang out is Purgatory, not far from the Salt Palace.
November 9, 2026 at 5:28 AM
Salt Shaker is a web UI for SaltStack that talks to your master through salt-api. Minions, key enrollment, compliance and drift checks, patching, a live command runner, jobs history, users and roles, OIDC single sign-on and an audit log. One container, AGPL-3.0.
Salt Shaker: A Web UI for SaltStack With Compliance Checks, Patching and SSO
SaltStack is a very good tool with a very thin interface. Most of what I do with a Salt master happens in a terminal: accept keys, run a command on a target, look up a job, check whether a minion drifted from its highstate. It works, but it does not scale to a team. Nobody else can see what ran, there is no audit trail beyond the job cache, and giving a colleague access means giving them a shell on the master. So I built Salt Shaker: a web UI for SaltStack that works through **salt-api**. It ships as one container with its own users, roles and audit log, and it can also run as a plain static app that signs in to salt-api directly. **AGPL-3.0** , React 19 on the front end, Hono and Better Auth on the server. The minions overview: status, OS, IPs, CPU, RAM and roles at a glance ## What it does **Minions.** Status, OS, IPs, CPU, RAM and roles in one table. A fleet breakdown flags minions running an older Salt than the master. Each minion has its own page with grains and compiled pillar. **Compliance.** Dry-runs the highstate (`test=True`) across a target and groups minions into in compliance, drifted, errors and no return, with a diff of what would change. One click remediates the drifted minions. Past checks are kept, so you can follow drift over time. **Patches.** Pending package upgrades across the fleet, viewed by package or by minion, with installed and available versions. Upgrade a single package where it is pending, or everything on one minion. **Enrollment.** Accept or reject keys after checking fingerprints. It also generates bootstrap commands, including pre-seeded keys, so a new minion is trusted on first contact. Enrollment: pending keys, fingerprints and bootstrap commands **Run.** Any execution module against any target type. Before you run, you see which minions the target matches. Results stream in live and state output is rendered with diffs. Risky commands on many minions need an explicit confirmation. **Orchestrate.** Runs `state.orchestrate` files with dry-run and pillar overrides, and shows step-by-step results with per-minion output. **Jobs.** Full results and a run-again button. With the server, jobs are recorded from the event bus and kept for 90 days by default, while the master itself keeps them for about 24 hours. That includes jobs started from the salt CLI, along with who ran them. **States and pillar, events, schedules.** Browse `file_roots` and `pillar_roots` with syntax highlighting. Watch the master event bus live with filters, with toasts for failed jobs and minions waiting for approval. Schedule nightly compliance checks, weekly patch scans or any function on a cron schedule. **Notifications.** Slack-format or JSON webhooks for drift, available upgrades, failed jobs and minions waiting for approval. There is also a Ctrl+K palette that jumps to any page, minion, saved target or recent command. ## Users, roles and SSO This is the part that makes it usable by a team. Salt Shaker has its own accounts, so nobody needs a Linux account on the master. * **admin** can do everything, including accepting keys and managing users. * **operator** can run states, commands, packages and orchestration, but cannot manage keys, users or files on the master. * **viewer** is read-only, and does not see pillar data, which often holds secrets. * **none** cannot sign in. Useful for switching off an account, or for SSO users who have no role yet. Single sign-on works over OIDC with Keycloak, Entra ID, Google, Authentik, Okta and others. Roles can come from IdP groups and are refreshed on every sign-in. PKCE and the id_token nonce check are in place. If you want a break-glass, set password login to admins only. Every change and every denied attempt lands in the audit log with who, what, where and the resulting jid. Local jobs also carry the user name in their job metadata, so `jobs.list_job` shows who ran them. ## How it works The server signs in to salt-api with one service account and listens to the master event bus. Every request from a user is checked against their role first and only then passed on, so the user's own credentials never reach salt-api. The database is SQLite by default or Postgres when you set `DATABASE_URL`. Several instances can share one Postgres: sessions, history and the audit log are shared, each scheduled run starts exactly once, and one instance, elected through a lease in the database, follows the event bus. If it stops, another one takes over within about 30 seconds. Dark mode ## Try it without a Salt master There is a demo mode with a simulated master running in the browser. Clone the repo, run `npm install` and `npm run dev`, then open `http://localhost:5173/?demo`. For the real thing there is a full local lab: `cd lab` and `docker compose up -d --build` start a Salt master with salt-api, three minions and the Salt Shaker container on port 8080. The first visit asks you to create the admin account, and the minion keys start out pending, so you accept them on the Enrollment page. The lab also includes a mock OIDC provider so you can try group-based roles. ## Deploying One container, published for linux/amd64 and linux/arm64 to GHCR. In its simplest form you give it the salt-api URL and a service account: docker run -d --name salt-shaker -p 8080:8080 -v salt-shaker-data:/data -e SALT_API_URL=https://salt-master:8000 -e SALT_API_USERNAME=salt-shaker -e SALT_API_PASSWORD=change-me -e SALT_API_EAUTH=sharedsecret -e PUBLIC_URL=https://salt.example.com ghcr.io/pipozzz/salt-shaker:latest Then open the URL and create the admin. The repo also has a `deploy/` folder with a complete Compose setup including automatic HTTPS through Caddy, in an SQLite and a Postgres variant. A few notes from running it: * Salt Shaker needs **Salt 3006 or newer**. * On the master, enable `rest_cherrypy`, and remember that Salt 3006 and later disable all netapi clients by default, so set `netapi_enable_clients` explicitly. * The service account is as powerful as the most powerful role you hand out. Keep its password in a secret store. * Put TLS in front, and if you proxy it yourself, turn off response buffering for `/api/salt/events`, because it uses Server-Sent Events. * Behind a reverse proxy set `TRUST_PROXY=1` so rate limits and the audit log see real client IPs. ## Direct mode If you do not want a server, the UI also runs as static files that sign in to salt-api directly with each user's own eauth credentials and permissions. Users, roles and the audit log are only available with the server, but for a small setup this is the lightest option. ## Things salt-api does that I had to handle Building this meant learning a few salt-api quirks on Salt 3007. The events endpoint rejects `?token=`, so the UI reads the SSE stream with `fetch` and an `X-Auth-Token` header. `jobs.lookup_jid` wraps state returns in an outputter structure. jids use the master's local time, so the UI learns the offset from wheel replies. And offline minions are detected the way the CLI does it, with `saltutil.find_job` and a short `gather_job_timeout`. These are written down in the README in case they save you time too. ## License and status Salt Shaker is licensed under AGPL-3.0 or later. If you run a modified version for others over a network, the license requires you to offer them the source, and the UI links to it from the sidebar and the login page. It is young and I am still adding to it, so issues and ideas are welcome. Documentation is at pipozzz.github.io/salt-shaker and the code is at github.com/pipozzz/salt-shaker. ## My take I wanted a Salt interface that treats the master like production infrastructure: roles instead of shared shell access, an audit log that records denied attempts too, and compliance and patching as first-class views rather than scripts I run by hand. The decision I care about most is that users never touch salt-api credentials. The server checks the role, then makes the call with the service account, and leaves the user's name in the job metadata. If you run Salt for a team, that alone is worth the container. * * * SALT SHAKER · OPEN SOURCE ### Give your Salt master a proper UI Try the browser demo with no Salt master, spin up the Docker lab, or point the container at your own salt-api. Everything is in the repo. github.com/pipozzz/salt-shaker
devopspack.com
November 2, 2026 at 7:17 AM
:saltstack: :docker: New Salt Release 3008.5 LTS is out! 🎉

Easily test and manage your Salt setups in a clean Docker container:

docker pull ghcr.io/cdalvaro/docker-salt-master:3008.5

🔧 Salt API, Salt SSH & production-ready config.
📚 Docs & usage examples.
💬 Feedback and PRs are welcome! […]
Original post on fosstodon.org
fosstodon.org
October 29, 2026 at 5:38 AM
Good catch on the new Docker release for 3008.5 LTS. Using `docker pull ghcr.io/cdalvaro/docker-salt-master:3008.5` works, but consider adding `--tag saltstack` to avoid pulling a stale version if you're not explicitly targeting that tag in your workflow.
October 29, 2026 at 8:25 AM
"Private key is 4" is the greatest cryptography fail since SaltStack raised "e = 1"
October 20, 2026 at 8:52 PM
Like, there have been worse keygen fuckups. But not many.
October 20, 2026 at 7:38 PM
Sigh, #salt is slop, and dropping features.
I've looked at https://www.rexify.org/ and I failed to find how it deals with secrets.
I guess I either switch to #puppet by way of #openvox, or unify my systems on #nixos (and swallow linux sloppification). Sigh.

#saltstack #saltproject #sysadmin […]
Original post on social.hackerspace.pl
social.hackerspace.pl
October 18, 2026 at 6:13 PM
:saltstack: :docker: New Salt Release 3008.3 is out! 🎉

Easily test and manage your Salt setups in a clean Docker container:

docker pull ghcr.io/cdalvaro/docker-salt-master:latest

🔧 Includes Salt API, 🆕 Salt SSH 🤩, production-ready config & more.
📚 Docs & usage examples.
💬 Feedback and PRs […]
Original post on fosstodon.org
fosstodon.org
October 3, 2026 at 12:59 PM
Onsite DevOps Lead role in Munich requires 8+ years DevOps experience, Linux/CI-CD/GitLab/Docker/SaltStack, and supports development, operations, and SLA-driven incident resolution.
Save What Matters
Curate Feeds | Make Collections | Customize Email Briefs
briefly.co
September 25, 2026 at 12:14 AM
Salt beacons run in salt-minion, emit events only on change: inotify for file integrity, load/diskusage/journal for anomalies. Cheaper than cron polling. Guide for https://www.valtersit.com/vault/deploy-salt-beacons-for-realtime-file-integrity-monitoring-03507e/ #saltstack #beacons #inotify
Deploy Salt Beacons for Real-Time File Integrity Monitoring
www.valtersit.com
September 24, 2026 at 8:00 PM
Ship Salt job results and audit events straight to Elasticsearch with the returner. Central config via master_job_cache means minions need zero ES knowledge. SaltStack https://www.valtersit.com/vault/stream-audit-events-to-elasticsearch-via-salt-returner-ef5c54/ #saltstack #returner #elasticsearch
Stream Audit Events to Elasticsearch via Salt Returner
www.valtersit.com
September 24, 2026 at 6:00 AM
Salt top files evaluate top-to-bottom, later matches win, so dev/staging/prod can share a base and diverge only in pillar overrides. Full walkthrough: https://www.valtersit.com/vault/multienvironment-top-file-with-pillar-override-precedence-6c2a90/ #saltstack #topfile #valtersit
Multi-Environment Top File with Pillar Override Precedence
www.valtersit.com
September 23, 2026 at 4:50 AM
Salt Master gitfs backend: turn a Git repo into a live state tree, no rsync. pygit2 per remote, cache in /var/cache/salt/master/gitfs, fetch on fileserver.update. Setup https://www.valtersit.com/vault/configure-master-gitfs-backend-for-gitbacked-state-trees-9de260/
#saltstack #gitfs #ValtersIT
September 21, 2026 at 9:30 PM
misread "Saltpack" in there and got scared for a second remembering the saltstack vulns lmao

looks interesting other than i don't see why care about this when there's signal for most uses and cwtch (which seems strictly better than this, DNS or endpoint could both deanon?) if you want decentralized
May 18, 2024 at 9:59 PM
FYI, I've just invented the term CAPS to collectively refer to Chef/Ansible/Puppet/Saltstack #DevOpsDays
December 3, 2024 at 3:31 AM
JWP Connatix seeks a DevOps Engineer (Remote - NL/UK) to build & scale petabyte‑daily video infrastructure. Work with Python/Go/Java/Rust, AWS, Kubernetes, Terraform + config‑mgmt tools. Exciting chance to shape global video SRE #DevOps #Kubernetes #Remote #VideoTech aihackerjobs.com/company/jwpc...
DevOps Engineer - JWP Connatix · AI Hacker Jobs
DevOps Engineer at JWP Connatix - Python, Go, Java, Rust, .NET, AWS, Kubernetes, Terraform, CloudFormation, SaltStack, Chef, Puppet, DevOps, Infrastructure, Remote, Netherlands, United Kingdom | Apply...
aihackerjobs.com
March 6, 2026 at 2:29 AM
Wat is saltstack toch een fijn product....

pillar data staat op je salt server, maar de servers moeten online zijn, zodat saltstack zijn pillar cache ofzo goed kan updaten....
August 24, 2023 at 8:27 AM
October 28, 2025 at 11:44 PM
Saltstack lets you specify uid and gid when creating users. I assume that better maintained alternatives do as well.
December 15, 2025 at 1:24 PM