Just tell the security team to handle it ๐
(My security team would NOT be amused by this joke suggestion)
I think we have ~400 microservices of varying types that deploy in many ways to many places (big proponents of using the right tools for the job rather than forcing preferred tools) and definitely in the last block. Although, as a DevOps guy my life would be a lot easier if we had a handful of monster monoliths, I understand it doesn't make sense for our scale. I can fantasize though, and this meme hits extremely close to home ๐
Tangentially, at my previous job we were in blocks 4 and 5 of transitioning away from a single monolith. Major issues arise when a "Java only shop for 20 years" start down this path with an extreme mindset of "we only use Java". Java kubernetes controllers? lmfao, no thanks (they wanted them though ๐)
This aligns with my experience with enterprise contract work. Generally need to have a pre-existing relationship to get a foot in the door. For me this has come from building strong relationships with other devs at the same company. Some of those devs will move on and go down the management track, the higher up they get, and depending on your relationship, the more likely they would want to bring you in for a specific thing since "I've seen RandomDevOpsDude implement this successfully before, why not get him to do it again?" style.
Absolutely, which is why I never linked to Reddit. So I'm already loving and prefferring lemmy over Reddit 100%!
I write a lot of bash scripts that end up running in automation in some fashion.
#!/usr/bin/env bash
set -euxo pipefail
Is pretty standard for me.
-e exit on error
-o pipefail exit on pipeline fail
-u error on unset variables
-x trace
How I have never heard of yq, I'm unsure, but thank you as I'm sure it will make life easier
I can help with golang and DevOps. Although golang for me is by necessity and not my main language, but happy to help where I can, to take load off of the admins.
I won't parrot the reasons, I think other comments captured that.
However, I would MUCH rather share links in professional circles to something called programming.dev that is specifically an instance about programming rather than "choose your random generic instance" that has porn, memes, shit posts, etc. and oh look, a programming community too.
Sometimes the audit is unavoidable. Recently went through one, and my first thought was "wait, people still use oracle jdk?". Thankfully not my job to deal with, but I guess some companies never migrated off which blows my mind, but, to each their own I guess. Oracle is coming around looking for a paydays.
Agreed.
Should be used as additional data points for dev teams to better understand how their process looks and effects it has on the software as a whole.
The tricky part is presenting the data in a way that prevents bias and conflict while still adding value, which often comes down to scoped access to the right people, and is kind of annoying to have to implement around business people not getting the wrong ideas from the data.
I agree that I suspect is websockets. From the source