chaosmonkey | Go client to the Chaos Monkey REST API | Microservice library
kandi X-RAY | chaosmonkey Summary
kandi X-RAY | chaosmonkey Summary
Go client to the Chaos Monkey REST API that can be used to trigger and retrieve chaos events. This project was started for the purpose of controlled failure injection during GameDay events.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- main is the main entry point for testing
- NewClient creates a new Kubernetes client .
- TriggerEvent triggers an event
- assumeRole will assume the given role .
- DefaultConfig returns a Config with default configuration
- printEvents prints the events
- listAutoScalingGroups returns a list of AutoScalingGroups
- decodeError decodes an API response body
- abort sends an error to stderr .
chaosmonkey Key Features
chaosmonkey Examples and Code Snippets
docker run -it --rm -p 8080:8080 \
-e SIMIANARMY_CLIENT_AWS_ACCOUNTKEY=$AWS_ACCESS_KEY_ID \
-e SIMIANARMY_CLIENT_AWS_SECRETKEY=$AWS_SECRET_ACCESS_KEY \
-e SIMIANARMY_CLIENT_AWS_REGION=$AWS_REGION \
-e SIMIANARMY_CHAOS_LEASHED=false \
simianarmy.chaos.leashed = false
simianarmy.chaos.terminateOndemand.enabled = true
simianarmy.chaos.asg.enabled = false
brew tap mlafeldt/formulas
brew install chaosmonkey
go get -u github.com/mlafeldt/chaosmonkey
Community Discussions
Trending Discussions on chaosmonkey
QUESTION
I am having a hard time in Chaos Monkey For Spring Boot regarding error responses when a user POSTs an invalid (like {"level": -2}
update via REST to our actuator endpoint where one can update options of the behavior of CMSB (only positive levels are allowed). In the first image, I set the management.server.port
to 8888
and the app port to 8080
. When posting a new property to the CMSB REST API I am getting the following response (which is not what we would have expected):
And in case I leave the management port at the same port the same as the app I am getting the following response:
For both cases we would have expected the same error response (the second one). So we're asking us (at CMSB) whether this is an intended behavior of spring boot and if not, what our options are to get around writing our own error response handler in case the management port is different from the app port.
Please note that this is not about the intended behavior of chaos monkey for spring boot but rather about whether this is a spring boot bug or not. In both cases we would like to have a detailed error response so a user knows what's wrong. Under the hood we are using the @Validated
annotation in combination with something like this to validate inputs:
ANSWER
Answered 2020-May-14 at 12:30Looks like the spring team fixed it here: https://github.com/spring-projects/spring-boot/issues/21036
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install chaosmonkey
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page