fault-injection

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

One problem with faulting programs under KRF is that KRF might decide to inject a fault during the dynamic link/load phase, aborting ld-linux.so instead of the actual target image. This usually isn't helpful, since it doesn't indicate any mistakes in the target itself.

It should be possible to check the loaded program's name via the current task, probably via comm. We should use that (or

simulate failure port is already allocated