nap VS http-add-on

I took a lot of inspiration from Hurl while building Nap[0]. My next goals for it are a UI and/or a VS Code extension.

[0] https://naprun.dev

I learned while building nap[0] that sometimes ideas just need to simmer. It’s like cooking. Sometimes there’s that one step that makes the meal work, like adding wine to a hot skillet.

I had the initial idea for Nap over a Christmas break and built a working prototype. It took another 2 years for me to see a good opportunity to even use it for myself! But that was a catalyst that helped turn it into a more mature tool. It still has very few users, but I’m very happy with it, and that’s enough for me.

[0] https://naprun.dev

I'm working on Nap[1], a fast, file-based framework for defining and running HTTP integration tests via the CLI.

The ultimate goal is to embed Nap into the SDLC--tests that are defined during development and then run during CI/CD. I'm closing in on a V1 release of the CLI tool, at which point I'll be looking to start expanding on the feature-set and add a UI.

I could use contributors who are comfortable building something Postman-esque as e.g. a VSCode plugin that could take advantage of the file-based nature of my project and make it more approachable for the masses.

[1]: https://github.com/davesheldon/nap

KEDA ships with an HTTP add-on to enable HTTP scaling.

KEDA has a special scaler that creates an HTTP proxy that measures and buffers requests before they reach the app.

I am a core maintainer on the KEDA HTTP Addon project (https://github.com/kedacore/http-add-on). It's 100% written in Go and we are a small group looking for additional contributors. I believe there are interesting challenges ahead of us that will be enjoyable to solve.

If you're interested, please reach out. My username here is the same as my username on the Gophers and Kubernetes slack groups.

(You're of course welcome to just go pick up an issue in the repo if you'd prefer)

The KEDA HTTP Addon project contains three major components: the operator, scaler and interceptor.

Hacking on the KEDA HTTP Addon, I found myself having to do something familiar:

First, we need to finish the minimal infrastructure. The components and supporting artifacts (Helm charts, CI scripts, etc...) are being built in PR #2, and once we have them completed, we will merge it [5]. Second, we need to establish a roadmap. We're beginning to outline it now and will finish it shortly after merging.