v1 (next/beta) is officially out - Feedback welcome

[ekristen]

This is a complete rewrite, seeking all feedback.

Quick Start/Install

brew install ekristen/tap/azure-nuke@1

OR grab from the next releases

Overview

Next Releases

This is a complete rewrite of the azure-nuke tool to take advantage of the dedicated library libnuke of which I'm the author. This library was build by taking the code from the original aws-nuke tool and building a dedicated and well tested library from it. I've since rewritten my implementation of aws-nuke to use it.

Why the Rewrite

The original implementation was hacked together by pulling parts of the original aws-nuke code out and I wasn't really happy with how the resources were implemented and the concept of tenant, subscription and resource level resources was frustrating.

Feedback Wanted

I want your feedback on the terminology and anything else you've like to provide comment on.

What's New

Regions (aka locations)

To keep things consistent and not to re-implement things, I've opted to use the libnuke/config package as it's well tested. With that in mind it does make some specific nomenclature usage like Regions instead of Locations in the configuration. If user feedback demands Locations I'll consider changing it.

Locations supported are global and all azure locations around the world. global refers to the tenant, again considering global vs tenant here, unsure at the moment, but using global

So if you want to target anything scoped to your tenant + subscriptions + resources in eastus your configuration would need to look like:

regions:
  - global
  - eastus

Configuration Changes

• tenants is deprecated in favor of accounts
• tenant-blocklist is deprecated in favor of blocklist

Note: this is mainly due to standardization around libnuke's terminology.

Resource Changes

Any resource that was using an uuid by default to represent itself has been moved to it's name and the ID is now a property. This affects how you write filters.

Builds

macOS builds are now signed! You do not have to approve them in security preferences any longer.