Hey :wave: DevOps / SRE here (~8y professional exp...
# random
k
Hey 👋 DevOps / SRE here (~8y professional experience). After constantly dealing with load testing setups, I built a tool to simplify the workflow (distributed tests, regression detection, reports, CI/CD, etc): https://loadtester.org Would love feedback from others engineers — happy to jump on a quick demo call if useful, otherwise feel free to register and use a free plan!
e
You scored on that domain!
💯 3
m
@Kristian Razum it might be overkill to create a parameterized function that specs out input parameters and creates the curl but… i can totally see a call to your service packaged as a Javascript GitHub Actions action, a Circle CI orb, or a Bitbucket Pipelines pipe. 🤔 Maybe even having a set of JSON files that get passed in as data with test details. I feel like that would me more manageable than hardcoded calls to
curl
. But at the same time I appreciate the elegant simplicity.
k
@Erik Osterman (Cloud Posse) Yes! Thank you @managedkaos We already have a feature on the New Test page that accepts a cURL command and auto-populates the test fields, preserving the URL, headers, user-agent, and request body. Also our Github/Gitlab CI/CD Integration page has a copy/paste ready example for the pipelines... As well as all of the options it can support
Regarding having the more simple "binary" rather than doing it all with curls, I appreciate this input VERY MUCH. I have thought about it, but never actually gave it that much attention, thank you for bringing this up.
👍🏾 1
m
No problem! I see the pattern in GitHub Actions where you can just pass in the parameters and have a function that wraps the call to the service. Easy enough to do with JS or a container (for Circle CI, Bitbucket, and/or CLI).