New Security Releases from Salt Project:
Salt v3006.12 LTS and v3007.4 STS are available!
https://saltproject.io/security-announcements/2025-06-12-advisory-3006-12-3007-4/
#Saltstack
I’m doing a company training on #saltstack and am curious how others like to structure #configuration_management trainings? Regardless of whether it’s #ansible or #cfengine or #puppet #chef etc. I think there’s got to be some common paths people find easiest to follow.
Do you start with examples of the syntax or with the architecture or do a quick start CLI demo first? How quickly do you dig into writing “hello world” and what directions do you like to explore? What are the hard and the easy parts for you and for the students?
@eniko I mean, we don't even get fully-automated #IT where any "#AI" could in theory perform as it's ripe for that.
- I mean, #automation in #AI exists, but noone's gonna drop #Ansible, #Puppet or #Saltstack (not even #Landscape & #MAAS) for #ChatGPT or similar bs.
#Protip: Ask "AI" fans if they would cobditionlessly entrust an "AI" with their financial details in full.
- Pretty shure none of them do.
Getting the feeling that #saltstack, especially on #FreeBSD is getting more and more maintenance intensive. Disconnected minions, git pillar not loaded, upgrades seem problematic (and for that reason still at the 3006.x branch). Never had this with #puppet…
Today #chatgpt told me this little trick , to make cmd.run idempotent in #saltstack.
In the Salt Project Community open hour this month, the team talked about the recent Salt 3007.2 STS release, the in-progress work to upgrade current Salt releases to use Python 3.11.x in relenv, and more!
some project ideas i'm planning on working on in the near-mid future:
- rewriting my qubes os config as salt states, then offering them as rpm packages. i have some nice stuff in here!
- making a foss alternative to those cringey resume makers. it supports json resume schema
- working on an actually good alternative to nextcloud and cryptpad
#qubes #qubesOS #saltStack #cryptpad #nextcloud #resume #jsonResume
New Release from Salt Project:
Salt v3007.2 STS is available!
https://saltproject.io/blog/2025-05-14-new-release-salt-3007-2/
🐳🧂 New Release: Salt Chlorine v3007.2 is out! 🎉
Easily test and manage your Salt setups in a clean Docker container:
docker pull ghcr.io/cdalvaro/docker-salt-master:3007.2
🔧 Includes Salt API, production-ready config & more.
📚 Docs & usage examples: https://github.com/cdalvaro/docker-salt-master
💬 Feedback and PRs are welcome!
Built for the community. Maintained with ❤️ by @cdalvaro
#SaltProject #SaltStack #DevOps #Docker #Containers #SaltAPI #Automation #IoT #Puppet
in other news:
Shout-out to awesome people on #saltstack discord for providing a quick work-around for a weird problem I found yesterday!
No endorsement for Discord though, as I kind of hate it as a support channel.
🌟 To all Qubes OS enthusiasts! 🌟
Continuing from our last meetup this Friday, we're diving into the exciting topics of Salt and Android in Qubes OS! 🎉 (see our homepage 🌐 )
Before we get started, we want to hear from YOU – whether you're based in Berlin or anywhere else in the world!
How have you incorporated Salt into your Qubes setup?
What are your use cases?
Share your experiences and let's learn from each other! 🌞
In the Salt Project Community Open Hour this month, the team talked about David Murphy retiring, revival of the Salt Project MacOS Working Group, and more.
i'm making my salts for my qubes set up distributable as rpms, which is also a convenient way to transfer them from domUs to dom0 in a more secure manner (since the rpms are signed)
what i'm unsure of is this: currently, i have one rpm that is my whole repo, and the repo contains topfiles that a user can enable individually. should i instead offer the vms (or bundles of them, in some cases) as individual rpms?
Have been playing around with PyInfra for config of physical servers up till the point of having container orchestration going. So far it feels like a great SaltStack alternative but obvs will take me several days to weeks to rewrite everything. Perhaps I'll iterate some more with just one module to find the right abstraction level before committing to a full rewrite. Some of the primitives are a bit more primitive, for example the apt.repo operation has no concept of signing keys and need to write the logic myself.
A Letter from David Murphy: Retiring from Tech
Serious thanks, to David, for all the work over the years in making Salt awesome and being a hero in the community!
https://saltproject.io/blog/2025-04-02-david-murphy-retires/
Salt Project posted notes from the March 20th, 2025 Open Hour call.
In this month’s open hour, we talked about the completion of Salt Project CI work, the recent release of Salt v3006.10 LTS, and more!
on the topic of salt states for qubes, i found this extremely cool repo: https://github.com/gonzalo-bulnes/qubes-mgmt-salt-user
brilliant way to organize the salts and distribute them imo
calling all qubes users who use salt! is there a way to target domUs with `state.highstate` when using many topfiles?
my repo is at https://git.sr.ht/~xyhhx/qubes-salts
(details in reply)
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst