-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explore how to integrate with Keptn #1772
Comments
Webhooks seem to be the best way for us to integrate with Keptn. They require some data to be sent to the webhook. We would have to find a way of supporting webhooks and allowing different integrations to use the same webhook structure, but make Tracetest capable of sending different data to different integrations. Example:
Still, a couple of problems to be solved. How would the test run? Should the user select a file or an existing test to run? If it's a file, should it be stored somewhere (GitHub for example)? |
Another strategy that we can use is to use With this plugin we are able to run docker commands whenever |
To integrate with Keptn now we opted to use keptn-contrib/job-executor-service since a user can configure freely how they can use Tracetest inside Keptn. Other alternatives (webhook and lifecycle toolkit) demand a lot of customization inside of Keptn and Tracetest to work properly, like creating another service just to list keptn hooks or embed Go code directly on Keptn engine, which doesn't make sense now given that we want to give power to our users to use our CLI to control their testing process. Our first documentation is ready at: https://github.com/kubeshop/tracetest/tree/main/examples/keptn-integration , that we submitted as documentation to Keptn Community and we will present at their community meeting next week. Our next steps on this initiative are: |
Exploration
Find out how we can provide a way for users to trigger a Tracetest operation to assert service correctness via Keptn,
They have an open issue about Trace SLOs and it has some content on how we can start the exploration.
The text was updated successfully, but these errors were encountered: