Zack Proser
Zack Proser
We've considered refactoring cloud-nuke to use the [AWS Cloud Control API](https://aws.amazon.com/cloudcontrolapi/). **Motivation**: Using Cloud Control for cloud-nuke would theoretically mean that cloud-nuke would support all AWS resources that can currently...
Ideally, we should update the GuardDuty Detector deletion logic to mimic: https://github.com/gruntwork-io/cloud-nuke/blob/master/aws/nat_gateway.go#L63 In case there are many Detectors in a given region. Also, determine how many Detectors can exist simultaneously.
To assist with hitting the IAM roles limit in AWS - we could use the ability to delete IAM roles - but to also provide a list of roles that...
**Describe the solution you'd like** Add functionality to create a new random branch name if one was not provided via the `--branch-name` command. This could make it easier to use...
The CircleCI job for git-xargs currently sets the main go package's `VERSION` variable to the `$CIRCLE_TAG` which is either the branch name or the tag name. This means that when...
In some places, git-xargs is forced to fall back to reading the error message value from GitHub's API responses, since the GitHub API can be inconsistent in what headers, status...
Per this question: https://github.com/gruntwork-io/git-xargs/pull/62#issuecomment-1006699457 It would be useful to be able to pass a flag to `git-xargs` that causes all Github API response headers to be dumped to STDOUT to...
**Describe the solution you'd like** With #49 , we'll have introduced support for draft pull requests. Ideally, we'd have test coverage for this feature as well, using any mocks that...
Jim's thinking: > "Should this tool do more to be "unix philosophy friendly"? E.g., Normally, you pipe things into the real xargs. Does that make sense to do here? >...
Related: https://github.com/gruntwork-io/fetch/pull/43