The playground is always up-to-date and has two useful tabs: one listing all supported GraphQL queries and mutations, and one listing all relevant defined data types. While these are considerably out-of-date, they are what have been linked above for reference.įor the current stable release of Litmus ( v2.14.0), the Auth API docs are still mostly accurate but the Server API docs are not.Ī workaround for up-to-date Server API docs we used was to leverage the “GraphQL Playground”, available at /api by default. Note: As of February 2023, the latest published docs for the Auth API only covers v2.0.0 and the latest published docs for the Server API only covers v2.9.0. we sent requests to the Auth REST API at /auth and to the Server GraphQL API at /api/query. With the Litmus frontend service exposed (e.g. Perform operations relevant to analytics/monitoring, etc.Perform operations on ChaosHub experiments.There are two APIs available for use with the standard Litmus Chaos installation that we took advantage of: In this blog post, we describe how we utilized the Litmus APIs to programmatically launch and track the progress of Litmus scenarios in our pipeline. Because of this, we needed to find a way to kick off our scenarios programmatically. However, we wanted to automate our simulations by running our Litmus Chaos scenarios through an Azure DevOps Pipeline. Typically, users leverage the Litmus UI ( ChaosCenter) to organize, launch, and monitor scenarios. In a recent engagement, our team was tasked with using Litmus to conduct a variety of complex experiments on Kubernetes clusters in a repeatable way. It allows teams to conduct controlled chaos tests on Kubernetes applications, which reveals infrastructure weaknesses or potential outages. Litmus Chaos is a CNCF-hosted open-source Chaos Engineering platform. Launching Litmus Chaos Scenarios Programmatically
0 Comments
Leave a Reply. |