11–16 of 16 posts
Some questions:
1. Is it possible to include headers at the workflow-level. I can't determine whether this is possible from reading the docs. Use case: include Authorization header for all tests/steps
2. Is it possible to run some command or query before a workflow/test/step. Use case: obtaining auth tokens
Just wanted to hop in here as founder of Checkly that I think this is awesome. Coded API checks, or checks living in your codebase make total sense. I'm also kinda humbled as I launched Checkly as an indie hacker couple years back and later went VC route. Being mentioned by name by an alternative is kinda really cool! Good luck StepCI team and let's make the web (and the APIs) more reliable!
Nice to meet you Tim. Checkly is an awesome tool and thank you for your comment! API monitoring is a very crowded space. Our approach is similar to HashiCorp with tools like Terraform, both philosophically (being open-source) and UX-wise (configuration as code). Our users can benefit from being able to self-host it and customise it according to their own needs
Earlier quoted context omitted.
Nice to meet you Tim. Checkly is an awesome tool and thank you for your comment! API monitoring is a very crowded space. Our approach is similar to HashiCorp with tools like Terraform, both philosophically (being open-source) and UX-wise (configuration as code). Our users can benefit from being able to self-host it and customise it according to their own needs
Hey! Yes, very crowded! But also ripe for change as me and you are doing. Very excited to see how people will use Step CI, Checkly and whoever else wants to join this mission.
Also how did you embed the workflow editor/results in the homepage?
This is awesome! Also how did you embed the workflow editor/results in the homepage?
My friend has mentioned in the post that the tool can be used as a library. The CLI and the Online Playground are just clients built on top of the library
Have a look at our docs: https://docs.stepci.com/guides/using-library.html
Congrats on the launch. I'm excited to try this out. Some questions: 1. Is it possible to include headers at the workflow-level. I can't determine whether this is possible from reading the docs. Use case: include Authorization header for all tests/steps 2. Is it possible to run some command or query before a workflow/test/step. Use case: obtaining auth tokens
1. Currently not and auth is a tricky subject
2. Not at the moment, but we have a proposal to allow custom scripts: https://github.com/stepci/stepci/discussions/47
Also, can I ask you what authentication system you use?