Zack Proser

@radicarl This is a great idea. Thanks for the suggestion. I'll look into it.

Sorry, this was version `v0.0.28` and I was installing the TLS scripts module from the AWS service catalogue. The module seemed to be installed correctly / as expected.

> In theory, it should only show that error if it can't publicly access the repo... Ah yeah, that is kind of my point though, the first couple of times...

Cool - thanks for confirming. I will take care of this.

Thanks for your report @rafaljanicki - could you please check to see if release [v0.19.1](https://github.com/gruntwork-io/cloud-nuke/releases/v0.19.1) resolves this issue for you?

I'm going to close this ticket out because I'm confident the issue described in the first post has been fixed. Hi @sapenteng, could I ask you to please open a...

smebyp1 is correct - we do have a feature request for this, but currently git-xargs only supports GitHub.

Looks like not just a terrific start, but ultimately pretty close to being merge-able! :clap:

This is pretty non-intuitive, but every time you add a new resource to cloud-nuke, you need to go [here](https://github.com/ellisonc/cloud-nuke/blob/c75b348b9c33dc6e83ae9d5993a1eb5729feda91/config/config_test.go#L12) and add the exact line `ResourceType{FilterRule{}, FilterRule{}},` the same number of...

Did a bunch of smoke testing locally: - Creating and nuking IAM users - Creating and nuking IAM users while excluding a special user via config file - Create and...