add --cleanup-aws option to remove *ANY* AWS allocated resource

[gserra-olx]

in particular:

• cloudwatch logs
• SQS queues

[cwaltken-edrans]

Agreed 👍

[VitorFalcao]

@cwaltken-edrans Are you already working on a fix? I would like to start contributing to the project and this issue seems interesting.

[cwaltken-edrans]

No, I'm not working on this one right now. Feel free to send a PR. I'm pretty sure we can get it merged.

…

On Thu, Oct 5, 2017 at 9:48 PM, Nope ***@***.***> wrote: @cwaltken-edrans <https://github.com/cwaltken-edrans> Are you already working on a fix? I would like to start contributing to the project and this issue seems interesting. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#157 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AaaDsUIaJP-13Xlq5S83antCsz3SeXzsks5spXjjgaJpZM4OrB0D> .

[VitorFalcao]

Thank you. Could you please give me some pointers, since I am new to the project? What other resources should the "--cleanup-aws" option delete?

[cwaltken-edrans]

Please take a look at: https://github.com/cwaltken-edrans/goad/blob/master/infrastructure/aws/aws.go
The code in this file is solely responsible for creating aws resources.

Resources to delete if present that come right to my mind would be:

• SQS-Queue
• Role for lambda function
• Lambda aliases
• Lambda functions
• CloudWatch logs associated to the lambda function

Ideally the cleanup code would also apply to the Docker infrastructure though to run goad on docker is still considered to be an experimental feature.
You could take a look at the cleanup code for each infrastructure and improve on that and reuse the code.

[thalesfsp]

Any update on it?

[cwaltken-edrans]

Right now, no one is working on this.