eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

215
active users

#saltstack

0 posts0 participants0 posts today
KungFuDiscoMonkey<p>Updating My Salt Extensions <a href="https://paultraylor.net/blog/2025/updating-my-salt-extensions/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">paultraylor.net/blog/2025/upda</span><span class="invisible">ting-my-salt-extensions/</span></a></p><p><a href="https://social.tsun.co/tags/packaging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>packaging</span></a> <a href="https://social.tsun.co/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>python</span></a> <a href="https://social.tsun.co/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>saltstack</span></a></p>
rvstaveren<p>Getting the feeling that <a href="https://mastodon.online/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>saltstack</span></a>, especially on <a href="https://mastodon.online/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a> 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 <a href="https://mastodon.online/tags/puppet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>puppet</span></a>…</p>
Qubes Users Berlin<p>🌟 To all Qubes OS enthusiasts! 🌟</p><p>Continuing from our last meetup this Friday, we're diving into the exciting topics of Salt and Android in Qubes OS! 🎉 (see our homepage 🌐 )</p><p>Before we get started, we want to hear from YOU – whether you're based in Berlin or anywhere else in the world!</p><p>How have you incorporated Salt into your Qubes setup? <br>What are your use cases? <br>Share your experiences and let's learn from each other! 🌞 </p><p><a href="https://mastodon.social/tags/QubesOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>QubesOS</span></a> <a href="https://mastodon.social/tags/SaltStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SaltStack</span></a> <a href="https://mastodon.social/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Coding</span></a> <a href="https://mastodon.social/tags/ShareYourUseCase" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ShareYourUseCase</span></a> <a href="https://mastodon.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a></p>
xyhhx 🔻 (plz hire me)<p>on the topic of salt states for qubes, i found this extremely cool repo: <a href="https://github.com/gonzalo-bulnes/qubes-mgmt-salt-user" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/gonzalo-bulnes/qube</span><span class="invisible">s-mgmt-salt-user</span></a></p><p>brilliant way to organize the salts and distribute them imo</p><p><a href="https://nso.group/tags/qubes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>qubes</span></a> <a href="https://nso.group/tags/qubesOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>qubesOS</span></a> <a href="https://nso.group/tags/saltStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>saltStack</span></a></p>
xyhhx 🔻 (plz hire me)<p>calling all qubes users who use salt! is there a way to target domUs with `state.highstate` when using many topfiles?</p><p> my repo is at <a href="https://git.sr.ht/~xyhhx/qubes-salts" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">git.sr.ht/~xyhhx/qubes-salts</span><span class="invisible"></span></a></p><p>(details in reply)</p><p><a href="https://nso.group/tags/qubes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>qubes</span></a> <a href="https://nso.group/tags/qubesOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>qubesOS</span></a> <a href="https://nso.group/tags/salt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>salt</span></a> <a href="https://nso.group/tags/saltStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>saltStack</span></a></p>
Carsten<p><span class="h-card" translate="no"><a href="https://konfigurationsmanufaktur.de/@netzwerkgoettin" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>netzwerkgoettin</span></a></span> </p><p>Macht irgendeines davon wirklich Spaß?</p><p>Sobald ich nur mit etwas komplexeren Datenstrukturen in Jinja ankomme, "zerreißt" es mir förmlich den Schädel.</p><p>Und gerade bei <a href="https://social.linux.pizza/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>saltstack</span></a> finde ich die Fehlermeldungen, wenn mal etwas schief geht, meist nicht super hilfreich.</p>
Elias Probst<p><span class="h-card" translate="no"><a href="https://freie-re.de/@qbi" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>qbi</span></a></span> <a href="https://mastodon.social/tags/SaltStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SaltStack</span></a>'s Pepper kann das auch: 😄<br><a href="https://github.com/saltstack/pepper/issues/219" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/saltstack/pepper/is</span><span class="invisible">sues/219</span></a></p>
DefectiveWings ✈️:verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@geerlingguy" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>geerlingguy</span></a></span> </p><p>Do you still recommend <a href="https://infosec.exchange/tags/ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ansible</span></a>? We're a <a href="https://infosec.exchange/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>saltstack</span></a> shop currently, but we're nervous given the most recent changes.</p><p>How's the health of the ansible project?</p>
Carlos D. Álvaro :apple:<p>For those of you having troubles with the migration of <br><a href="https://fosstodon.org/tags/SaltProject" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SaltProject</span></a> to <a href="https://fosstodon.org/tags/Broadcom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Broadcom</span></a>, and if you use <a href="https://fosstodon.org/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Docker</span></a>, you can check <a href="https://github.com/cdalvaro/docker-salt-master" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/cdalvaro/docker-sal</span><span class="invisible">t-master</span></a> for running salt-master containerized.</p><p><a href="https://fosstodon.org/tags/SaltMaster" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SaltMaster</span></a> <a href="https://fosstodon.org/tags/SaltStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SaltStack</span></a> <a href="https://fosstodon.org/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DevOps</span></a> <a href="https://fosstodon.org/tags/Containers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Containers</span></a> <a href="https://fosstodon.org/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Docker</span></a> <a href="https://fosstodon.org/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IT</span></a> <a href="https://fosstodon.org/tags/SaltAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SaltAPI</span></a> <a href="https://fosstodon.org/tags/Infrastructure" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Infrastructure</span></a> <a href="https://fosstodon.org/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Podman</span></a></p>
🇺🇦 Sven Seeberg<p><span class="h-card" translate="no"><a href="https://social.tsun.co/@kfdm" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>kfdm</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@eliasp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>eliasp</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@isotopp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>isotopp</span></a></span> the decline of Saltstack is continuing. They shut down the repo.saltstack.io repos and switched to packages.broadcom.com. AFAICT they notified the community only 1 week in advance: <a href="https://saltproject.io/blog/upcoming-salt-project-docs-and-repo-migration/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">saltproject.io/blog/upcoming-s</span><span class="invisible">alt-project-docs-and-repo-migration/</span></a></p><p>And the best: packages.broadcom.com does not support IPv6. I have dozens of servers right now that cannot update packages. 😡 </p><p><a href="https://gruene.social/tags/Broadcom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Broadcom</span></a> <a href="https://gruene.social/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>saltstack</span></a></p>
Pete WrightOK sounds like <a class="hashtag" href="https://nlogic.systems/tag/broadcom" rel="nofollow noopener" target="_blank">#Broadcom</a> is royally screwed everyone here. From the salt-users mailing list:<br><br>"No, the old infrastructure will disappear at the end of the month. This is something that is being mandated by Broadcom. We were only able to work out the details of what is happening and options available to us this week as it is affecting all of VMware, not just Saltstack.<br><br>Sorry for the late notice. We are doing the best we can to handle the pain points. Unfortunately, there will be many changes related to this. Things won't be as pretty as they were before."<br><br>RIP developers, I'm not sure how <a class="hashtag" href="https://nlogic.systems/tag/salt" rel="nofollow noopener" target="_blank">#salt</a> and <a class="hashtag" href="https://nlogic.systems/tag/saltstack" rel="nofollow noopener" target="_blank">#saltstack</a> survive this, my team is already starting work to rewrite all of our config mgmt code to use <a class="hashtag" href="https://nlogic.systems/tag/ansible" rel="nofollow noopener" target="_blank">#ansible</a>.
Pete Wrightthis actually looks ways worse than i first imagined...the docs still haven't been updated, they still refer to the old saltstack domain for installing via packages.<br><br>any other <a class="hashtag" href="https://nlogic.systems/tag/salt" rel="nofollow noopener" target="_blank">#salt</a> <a class="hashtag" href="https://nlogic.systems/tag/saltstack" rel="nofollow noopener" target="_blank">#saltstack</a> admins or users out there heard of this cutover before today? i don't remember seeing anything on their mailing list i'm sub'd to until today.
Pete Wrightholy smokes, <a class="hashtag" href="https://nlogic.systems/tag/saltstack" rel="nofollow noopener" target="_blank">#saltstack</a> project dumping this a few days before the end of month on the community:<br><br><a href="https://saltproject.io/blog/salt-project-package-repo-migration-and-guidance/" rel="nofollow noopener" target="_blank">https://saltproject.io/blog/salt-project-package-repo-migration-and-guidance/</a><br><br>"In order to integrate with Broadcom infrastructure and policies, we are migrating off of AWS public cloud infrastructure and consolidating services used by Salt Project by end of October 2024."<br><br>and it was published on...drum roll please:<br>"by Salt Project Team — Oct 28, 2024"<br><br>well played broadcom, i guess if you screw all your users royally they'll leave and you won't have to support them anymore.
Elias Probst<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@isotopp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>isotopp</span></a></span> …advised them to put it under an umbrella of an independent organization/foundation to be free of any vendor-shenanigans and to allow for more community contributions. Some understood, but didn't have the power to change things. Some had the power, but didn't understand.</p><p>Goodbye <a href="https://mastodon.social/tags/SaltStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SaltStack</span></a> - it was (mostly) nice while it lasted!</p>
Elias Probst<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@isotopp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>isotopp</span></a></span> you can basically remove <a href="https://mastodon.social/tags/SaltStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SaltStack</span></a> from the list - since the <a href="https://mastodon.social/tags/Broadcom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Broadcom</span></a> acquisition, it's pretty much dead:<br><a href="https://github.com/saltstack/salt/graphs/commit-activity" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/saltstack/salt/grap</span><span class="invisible">hs/commit-activity</span></a></p><p>It'll rot for a few more years until either the community will realize what they're about to lose and fork the code &amp; project to revive it and get rid of the current bottleneck of a dead maintainership or it'll just fade away into irrelevance.</p><p>Back when I still had a lot of contacts into SaltStack/VMware, I warned them over and over again of this…</p>
Lady of Mystery and Science<p>At work, we use <a href="https://xeno.glyphpress.com/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>saltstack</span></a> (🤮), which touts itself as a perfectly fine replacement for things like ansible or puppet.<br>Today, I found a machine that had been running a salt command for 41 days(!) and never finished, had no way to alert a person to problems, and I only discovered it because the machine had other problems.</p><p>What chumps decided that this was a good idea?</p>
viq<p><a href="https://social.hackerspace.pl/tags/SaltStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SaltStack</span></a> seems to be going crazy on my systems, so I'm setting it up to be restarted if it goes over certain amount of memory, using <a href="https://social.hackerspace.pl/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> resource limits on <a href="https://social.hackerspace.pl/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a>, and <a href="https://social.hackerspace.pl/tags/monit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>monit</span></a> on <a href="https://social.hackerspace.pl/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenBSD</span></a>. <br><a href="https://social.hackerspace.pl/tags/sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sysadmin</span></a></p>
Elias Probst<p><span class="h-card" translate="no"><a href="https://kanoa.de/@pluhmen" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>pluhmen</span></a></span> heute würde ich <a href="https://mastodon.social/tags/SaltStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SaltStack</span></a> nimmer im Unternehmensumfeld einsetzen.<br>Bereits die Übernahme durch <a href="https://mastodon.social/tags/VMware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VMware</span></a> hat intern einiges durcheinandergebracht, auch wenn VMware dann tatsächlich beträchtliche Ressourcen in das Projekt gesteckt hat. Die <a href="https://mastodon.social/tags/Broadcom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Broadcom</span></a>-Übernahme hat es vollends gekillt.</p><p><span class="h-card" translate="no"><a href="https://mastodon.online/@unixtippse" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>unixtippse</span></a></span></p>
René Mayrhofer :verified: 🇺🇦<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@ask" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ask</span></a></span> Thanks! You are of course right about atomic updates. I take that risk at the moment for my personal family installation because of very limited change activity on the server side, but for a larger work/university group, that would potentially be an issue.</p><p>You are also right about backing up the .env file. I missed that in my post because all my containers are managed through <a href="https://infosec.exchange/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>saltstack</span></a> and I have that config backed up in a separate Git repository anyways. However, it makes sense to mention the .env in my post as well - will update :)</p>
Aner :linuxmintnew:<p>Guess I've been on here long enough to do an <a href="https://fosstodon.org/tags/introduction" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>introduction</span></a> I'm Chris, and I live in <a href="https://fosstodon.org/tags/Bermuda" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Bermuda</span></a></p><p>I'm married with two kids, a son and a daughter.</p><p>My hobbies include <a href="https://fosstodon.org/tags/mountainbiking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mountainbiking</span></a> <a href="https://fosstodon.org/tags/gaming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gaming</span></a> (including <a href="https://fosstodon.org/tags/TTRPG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TTRPG</span></a> <a href="https://fosstodon.org/tags/DnD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DnD</span></a> and <a href="https://fosstodon.org/tags/MagicTheGathering" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MagicTheGathering</span></a>) and <a href="https://fosstodon.org/tags/spearfishing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>spearfishing</span></a>.</p><p>I work currently as an <a href="https://fosstodon.org/tags/IaaS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IaaS</span></a> Support Engineer at a <a href="https://fosstodon.org/tags/cloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cloud</span></a> and <a href="https://fosstodon.org/tags/datacentre" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>datacentre</span></a> provider. I do everything from setting up virtual environments, and orchestration through <a href="https://fosstodon.org/tags/SaltStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SaltStack</span></a> to <a href="https://fosstodon.org/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DevOps</span></a> and managing our <a href="https://fosstodon.org/tags/Networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Networking</span></a> and <a href="https://fosstodon.org/tags/Switching" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Switching</span></a> platform.</p>