I Performed Necromancy on a 2010s Ruby Gem and It's Fine Now
·7 mins
Soap4R-ng just got its first real release. Turns out reviving a 15-year-old SOAP library is 90% rebuilding CI that quietly died years ago and 10% SOAP.
Open-Source
Postman Prometheus
Fork: github.com/rubyjedi/postman-prometheus
Upstream: postman-prometheus
The original postman-prometheus tool was useful: run a Postman collection, export the results as Prometheus metrics. One shot, one collection.
What I needed was: run several collections, continuously, all feeding into one /metrics endpoint. The idea being that your Postman collections — which already describe your API contracts — double as live health checks you can scrape with Prometheus and visualize in Grafana.
Soap4R-ng
Repo: github.com/rubyjedi/soap4r
Back in the early 2010s, a lot of enterprise Ruby on Rails apps were neck-deep in SOAP integrations — insurance carriers, healthcare systems, EDI pipelines. The de-facto library for that was soap4r. And then it went unmaintained right as Ruby was moving past 1.8.