View Code? Open in Web Editor
NEW
A resiliency tool that automates Failure mode effect analysis tests, simplifying complex testing with a behavior-driven development and testing approach. Provides a programmatic way to execute controlled failures in AWS and a BDD way to write test cases, allowing test plans themselves to become test cases that can be executed as is.
License: Apache License 2.0
Java 96.33%
Shell 0.89%
Gherkin 2.78%
cloudraider's People
cloudraider's Issues
Refine overall directory structure of the repo and put all images under single directory.
We want to setup a mock service on AWS. Looking for ways to automate this entire setup.
On this mocked service setup, we want to run FMEA suite using cloud raider.
Is your feature request related to a problem? Please describe.
Ppl often work with multiple aws accounts and often run scenarios or api calls inadvertently on the wrong aws account.
Describe the solution you'd like
Take acc no in the config and validate before performing any operations
Describe alternatives you've considered
This is usefull for a generic scanario where the names of ELB/ec2/tags are same across accounts
Following things should be achieved:
Explore way to run Cloud Raider Core Library in Pipeline
Setup CI/CD pipeline
Is your feature request related to a problem? Please describe.
Create an exhaustive documentation of all the features given by cloud raider core library.
Describe the solution you'd like
Documentation can be created under this specific folder as markdown file.
The documentation needs to be structured with the basic steps including the following:
First Time Users contributing to the app
First Time Users/Services using Cucumber Client
First Time Users/Services using Java Client
These individual documentations can exist in their respective directories.
Describe the bug
First time users are unable to figure out the mvn commands to build the library and run the scenarios with the client
Expected behavior
A precise step by step guide for first time users to execute their first failure
Is your feature request related to a problem? Please describe.
We work with multiple aws accounts and the ability to have multiple config files is really helpfull with each config file for each account
Describe the solution you'd like
support passing config files in command line as mvn param
Describe alternatives you've considered
Having a single config file for multiple accounts in confusing and error prone.
Describe the bug
When trying to block port the command fails to do what is expected and errors out
To Reproduce
run the port block feature
expected port block but got this message:
iptables v1.4.21: invalid port/service {0}' specified Try
iptables -h' or 'iptables --help' for more information.
iptables v1.4.21: Port "{0}" does not resolve to anything.
Make the core Cloud Raider library compatible with the latest Java version.
Describe the bug
ssm servers are blocked when performing network failure scenarios, hence the scenario fails
To Reproduce
Run a network failure scenario which blocks ssm messaging
Expected behavior
SSM has to be bypassed from the failure as failing the communication channel breaks the test.
Add required tools to report and measure test coverage and put it back as label/hook on README.
Write a configurable script (shell, etc.) to run fmea tests using cucumber client.
Script should accept the required parameters of AWS environment and should be able to run FMES tests on the service with minimal efforts required from first time consumer of Cloud Raider.
Describe the bug
PR build is broken
To Reproduce
create a PR
Expected behavior
PR build succeeds on tests passing
Screenshots
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Additional context
travis install dependency fails