#devoops — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #devoops, aggregated by home.social.
-
As the cost for building software is shrinking fast, the cost for running software is going to grow faster, and guess what cost most orgs never planned for. #devoops
-
TIL: Clicking "Remove" on a #Proxmox pool member seems to remove the whole VM instead of just the membership 🫠
- Sent by my removed FreeIPA master node
UPDATE: Nope, it was a off-by-one error with VM IDs. Was also running "terraform destroy" in the background - so TIL: never do two things at the same time. 🤡
-
After some #devoops, 20 pictures where taken.
After some swearing and a 'turn it of and back on again', 20 pictures were bluetoothed to a laptop and cropped square.
29 basic lines of html, css, and js later, and there is a minimal "roll a 20 sided die" app ready to deploy!
https://gitlab.com/jezra/golden20 -
We had some issues with indexing hashtags over the last day or so, this has now been fixed #DevOops
-
OH on slack:
> The world needs more musical post-mortems. https://www.youtube.com/watch?v=p03oO_7sCaY
-
My code editor has been opened so that I can write a script/app to make 3 http api calls; but I'm stuck on determining which language I should use to make coding mistakes with.
#devoops :) -
OH on slack: sometimes you think, "Oh, a regex could solve this." Now you have two ~problems~ administrators on your github repos
-
Interesting, so installing helm charts with #terraform is a .. not great experience when things don’t go exactly right.
Somehow this chart made it into state when it never successfully rendered the tf resource.
I can’t remember if that means the provider behavior is to run a destroy against it on failure or not and if so the chart itself isn’t working as expected for some reason.
Time to read more docs and hopefully not looking at provider code.
-
Hab mal ein Monorepo vorgeschlagen in einer Runde von knapp 20 Leuten: Freelancer, Architekten, Entscheider. Es wurde heiss diskutiert, niemand wusste, wie man mit etlichen Repos umgehen sollte oder wollte, und mit den nötigen Credentials.
Das Wort „Monorepo“ fiel, der Architekt fing erst an zu brüllen, dann zu weinen: „nein, keine Monorepos. Ich WILL kein Monorepo!!!“Monorepo anyone?
-
By way of a Project Manager at work:
-
Und das ist der Grund warum man Anwendungen immer auf Englisch benutzt :D
-
Und das ist der Grund warum man Anwendungen immer auf Englisch benutzt :D
-
Und das ist der Grund warum man Anwendungen immer auf Englisch benutzt :D
-
Und das ist der Grund warum man Anwendungen immer auf Englisch benutzt :D
-
Und das ist der Grund warum man Anwendungen immer auf Englisch benutzt :D
-
OH on slack:
SREcon 2024: hey, just a crazy thing, but we thought about giving the root password to a parrot. What do you think?
SREcon 2025: here's our comprehensive report from parrot's rampage, after equipping it with root password and a spending account
SREcon 2026: codebases should be parrots, not pets
SREcon 2027, presented mostly by parrots: how to work effectively with grumpy humans
-
Vibe coding and imposter syndrome:
-
OH on slack
User Story
As Overloaded Olivia, the backend engineer,I want clear, actionable requirements with business context, so that I can implement the correct solution without burning half a day in meetings or wild guessing.
Acceptance Criteria
1. The story includes functional requirements (not just vibes).
2. Success/failure states are defined happy path + edge cases).
3. Any dependencies or blockers are identified.Bonus: PM/Designer reviewed this and it’s not just a draft in disguise.
-
Monday Morning Mishap:
Me: “Why is the firewall blocking prod?”
Also me: “Oh… I was testing that last night.”Pro tip: Don't debug your weekend experiments in production. (But let’s be honest… we all have.)
-
OH on slack: I think we've all seen enough to say that computers are a cryparty. it's just very rarely they're tears of joy; most often they're tears of sorrow or rage or shock.
-
-
Bit of "fun" with O365 email for us this week...
Background: Our main email domain's MX records are on-prem servers that do a bunch of things, and email for our O365 domain relays through them. These on-prem MX servers have been dual-stack (ipv4 and ipv6) for many years now.
Not sure exactly when MS made various changes, but our example-com.mail.protection.outlook.com records have both ipv4 (A) and ipv6 (AAAA) addresses.
And they enforce that email they receive has to be via a "trusted connector" for your domain, pass SPF, or pass DKIM.
> 450 4.7.26 Service does not accept messages sent over IPv6 [dead::beef::1] unless they pass either SPF or DKIM validation (message not signed)
But O365 doesn't yet support adding ipv6 IPs/ranges to the trusted/connector list.
So, suddenly email sent to us without DKIM signatures was getting stuck in the MX server queues.
Our temporary workaround is we added egress firewall rules on the MX servers themselves blocking SMTP to 2a01:111:f400::/48 and 2a01:111:f403::/48 (the published ranges for their MX servers). Not ideal, but at least mail is flowing again.
-
“absolutely no api keys have been exposed while training our language model. no, not even your automated pornhub submission key, mr. brian lafarge of the lafarge llc, 34 wicklow gate E, milton keynes MK9 3AT, UK, you dirty bastard”
#WhatCouldPossiblyGoWrong #LLMNonsense #DevOOPS
https://circumstances.run/users/mawhrin/statuses/110354772916258618 -
where's the wisdom in this project?