If like to understand how you are using it as a library.

I appreciate the PR. V3 isn't out yet so I'm hesitant to switch. I have another project of mine staged to switch just waiting on its release.

I'm not using it yet as a library, just considering it. aws-nuke would be part of a larger AWS account management service, something that would be responsible for cleaning accounts, where the value of including aws-nuke as a dependency would be to not need to track all of the different AWS services to clean. I could shell out, but there should be more control with context.Context compared to SIGTERM.

If you are going to use it at a library you should look at how the nuke command is implemented and re-implement that function minus the CLI part in my opinion.

You can pass context to the CLI right now too with v2 via os.RunWithContext if I recall correctly.

Either way, v3, is high on my radar, but until it hits it's release I will likely hold on updating it here, or I need better test coverage to ensure things still work properly.