Suspend processes

[SaiVishwas]

Fixes #119

Assumption: In the desired/target state, only the processes mentioned in the input yaml need to be suspended on the ASG
Scenarios tested:
During Create

1. When the suspendProcesses config is not present, then no action taken
2. When the config is passed, post ASG creation, the processes mentioned are suspended using a single AWS API call

During Update

1. When the target list mentioned in yaml is different from current list of suspended processes in ASG, only then it is updated (resumed/suspended)

@eytan-avisror please review and let me know if you would like me to improve anything.
Thank you

[CLAassistant]

All committers have signed the CLA.

[codecov]

Codecov Report

Merging #132 into master will decrease coverage by 0.43%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master     #132      +/-   ##
==========================================
- Coverage   88.93%   88.49%   -0.44%     
==========================================
  Files          10       10              
  Lines        1193     1217      +24     
==========================================
+ Hits         1061     1077      +16     
- Misses         91       95       +4     
- Partials       41       45       +4     

Impacted Files	Coverage Δ
controllers/provisioners/eks/create.go	92.85% <0.00%> (-2.27%)	⬇️
controllers/provisioners/eks/update.go	96.58% <0.00%> (-0.84%)	⬇️
controllers/provisioners/eks/helpers.go	87.46% <80.00%> (-0.47%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5e020b3...6a1fe67. Read the comment docs.

[eytan-avisror]

Thanks for the PR and contribution @SaiVishwas
Some minor comments added.

[eytan-avisror]

Thanks for the comments you addressed @SaiVishwas .. looks great!
Added few last things we need to change.
Also, I noticed there is a coverage drop, can you run make coverage and check? or look in the codecov report and see if you can add a test?
It's not a significant drop, but might be good to check if it's something we want to cover

[SaiVishwas]

Hi @eytan-avisror ,
I have made the suggested changes. The newly added methods are being tested as part of the unit tests. I went through the code coverage report and drop in coverage is due to the

err != nil { return err }

code block.

Thank you

[eytan-avisror]

Thanks @SaiVishwas
We should be able to merge this shortly, had one more question above.

[eytan-avisror]

Amazing work @SaiVishwas 🥇

[eytan-avisror]

15 scenarios (15 passed)
72 steps (72 passed)
22m41.99080058s
testing: warning: no tests to run
PASS
ok github.com/keikoproj/instance-manager/test-bdd 1362.315s [no tests to run]