-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 3 #16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ekristen
added a commit
that referenced
this pull request
Jan 30, 2024
* initial rewrite of aws-nuke using libnuke * fix: gitignore * fix: add missing workflows * fix: disable push for branches * fix: do not run goreleaser on prs by default * fix: say yes to all cosign prompts * fix: the tags in which goreleaser builds * fix: goreleaser config * version: 3.0.0-beta.1 * fix: Dockerfile BREAKING CHANGE: tool no longer runs off default command, must use subcommand
ekristen
added a commit
that referenced
this pull request
Jan 30, 2024
* initial rewrite of aws-nuke using libnuke * fix: gitignore * fix: add missing workflows * fix: disable push for branches * fix: do not run goreleaser on prs by default * fix: say yes to all cosign prompts * fix: the tags in which goreleaser builds * fix: goreleaser config * version: 3.0.0-beta.1 * fix: Dockerfile BREAKING CHANGE: tool requires a subcommand to run properly
corybekk
pushed a commit
to oreillymedia/aws-nuke-v2
that referenced
this pull request
Nov 5, 2024
* initial rewrite of aws-nuke using libnuke * fix: gitignore * fix: add missing workflows * fix: disable push for branches * fix: do not run goreleaser on prs by default * fix: say yes to all cosign prompts * fix: the tags in which goreleaser builds * fix: goreleaser config * version: 3.0.0-beta.1 * fix: Dockerfile BREAKING CHANGE: tool requires a subcommand to run properly
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This project is now standalone from it's upstream aws-nuke. This was originally a managed fork, but now due to how much the code bases have diverged this is no longer considered a fork.
Notable Changes
Remove
andLister
functionsdocs/
published to ekristen.github.io/aws-nukeBreaking Changes
nuke