-
Notifications
You must be signed in to change notification settings - Fork 125
Added Azure VM Chaos by running Powershell script based chaos #743
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
@ispeakc0de @uditgaurav @ksatchit - Any updates on review? |
@jakub-dzon @masayag @torumakabe @elric1 - can i get some review on this? |
Signed-off-by: Author Name [email protected] Signed-off-by: SSanjeevi <[email protected]>
Hi @SSanjeevi, I haven't been working nor contributing to this project in past years, so I cannot provide meaningful review for your PR. However, have you tried joining litmus slack channel to draw direct attention from the maintainers? (join slack from link in https://litmuschaos.io/ ) |
@masayag Looks like I need an invite to join that Kubernetes slack. - can you pls invite me? |
sure, I need your email address to invite. |
|
@masayag - did you invite me? |
yes, I did. |
@SSanjeevi can you check again? Perhaps now after reapplying? |
What this PR does / why we need it:
Added Azure VM Chaos by running PowerShell script on start of chaos to create the chaos and at end of Chaos runs another PowerShell script with parameters to complete the chaos. This will open way for many custom Chaos which can be run with the option of PowerShell script instead of predefined Azure operations.
Which issue this PR fixes
This PR is new enhancement of adding new experiment
Special notes for your reviewer:
Am new to Go lang don't have much debug knowledge - so created this draft PR, please someone test it and merge this.
Checklist:
breaking-changes
tagrequires-upgrade
tag