Issue Description

Question

Describe what happened (or what feature you want)

Trying to evaluate ChaosBlade as an option for resiliency testing. But I'm not sure if this is a feature request or a question. Actually, two questions:

• Does ChaosBlade support Azure, or can it be extended to support Azure?
• Can ChaosBlade inject failures into a Platform as a Service (Pa

refs to https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/envtest#pkg-constants, the actual usful env is USE_EXISTING_CLUSTER not TEST_USE_EXISTING_CLUSTER, and we have used the former for a while. 😰

Currently, we have a lot of env vars in the litmusportal, so we need to use envconfig pkg to validate and process the env vars.
PKG- https://github.com/kelseyhightower/envconfig

Need to add in:

• graphql-server
• event-tracker
• subscriber
• authentication-server

Running 2.9.1 (yes, I know, it's old). We have several different clusters, but don't have the same k8s deployments in each cluster. Tried to use a generic policy definition. When it is applied in a cluster which doesn't have one of the deployments, seal doesn't handle the 404 from k8s and dies. Yes, we can change the policies, but also seal shouldn't die in this scenario.

While this was wit

Currently this will work:

"method": [
        {
            "name": "send-invalid-request",
            "type": "action",
            "provider": {
                "type": "process",
                "path": "echo",
                "arguments": "${request_file}"
            }
        }
    ]

But this won't:

"method": [
        {
            "name": "send-invalid-

Currently the docs dont tell you how to execute runtimeassaults. Theyre only get executed either by a scheduled cron expression or by executing a POST REST call to /actuator/chaosmonkey/assaults/runtime/attack