HN user

dschofie

115 karma

Telophase S23

Posts16
Comments16
View on HN

Reading through the post it looks like this infects via preinstall?

The new versions of these packages published to the NPM registry falsely purported to introduce the Bun runtime, adding the script preinstall: node setup_bun.js along with an obfuscated bun_environment.js file.

Definitely! A lot of this falls under the "reachability" umbrella. It's just a little harder to say if something is actually used vs just installed. For example, in your app you could exec a script which can be harder for tools to detect with accuracy and there are just quite a few edge cases to handle

I believe the problem comes where there isn't a clear division of ownership between product teams and SREs.

At a previous company, we embedded SREs on teams for a quarter rotation and found that this model worked well. It was nice to give SREs more product team empathy and vice versa

Spotify Is Screwed 3 years ago

This feels like a clickbait title. I don't think that Spotify is in that unique of a position compared to other tech companies that have gone through "hypergrowth" and are now focusing more on profitability.

Thanks for sharing! It would be cool to share a loom or a sample dashboard to get things going, as I'd love to see a little more before signing up. It's hard for me to tell where this fits in. Is it a replacement for early usage of datadog? Does this offer support like pagerduty for pinging me? Is it the devX of setup?

Congrats on the launch!

Hi, we made configtailor to manage the growing number of JSON config files that we managed for every environment and cell that we maintained.

configtailor generates config files based on any dimension that you input. For example, we have cells (us0, us1, ..., us9) and we have microservices. For internal microservice discovery we use DNS with the following URI `us0.microservice.path`. We were copying and pasting into each cell's config file the path per cell along with dev and test environments. With configtailor we can put in `$cell.microservice.path` and have configtailor generat the appropriate config.

Some other benefits: - Easily set config values that can be reused in each environment. For example, setting a base config value that is only overwritten for tests. - Hooks into what people are used to with other Go tools that generate other files.

Overall, I was excited to open source this because our config files were a copy/paste nightmare and this tool helped us keep our config DRY and prevents people from missing values.

Let me know what you think!