chaos-engineering

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

Feature Request

Is your feature request related to a problem? Please describe:

When some syntax error occurs in generated file "zz_generated.**.go", "chaos-builder" will not work well.

Describe the feature you'd like:
when "walkthrough" the path, ignore the .go file that start with zz_generated

Describe alternatives you've considered:

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-

I would like to drop Spring Boot support for 1.5.x. It is EOL https://spring.io/blog/2018/07/30/spring-boot-1-x-eol-aug-1st-2019
I would also add some notes in the docs, that we adhere to the spring boot lifecycle in order to be transparent about dropping support for versions.