-
Notifications
You must be signed in to change notification settings - Fork 724
Cannot Destroy IOTAuthorizer
#1251
Comments
What do the logs say once it fails out? It should give the actual reason for it failing after it's tried 3 times. |
Was looking at the logs, did not find anything there actually. But I see you already merged a fix, so I'll give it a try and let you know how it went! |
I just realized the merged PR was actually from a diff repo https://github.com/ekristen/aws-nuke and learned that version 3 is prolly what I should be using. So.... will need to check that a bit for starters. 🙂 |
Yeah, sorry, I try to help people but not push my fork directly too much, trying to be respectful. Let me know if you run into issues. I was able to replicate it locally. :) |
@adrians5j this issues has been fixed via ekristen/aws-nuke#241 Please see a copy of the notice from the README about the deprecation of this project. Sven was kind enough to grant me access to help triage and close issues and pull requests that have already been addressed in the actively maintained fork. Some additional information is located in the welcome issue for more information. Caution This repository for aws-nuke is no longer being actively maintained. We recommend users to switch to the actively maintained fork of this project at ekristen/aws-nuke. |
Thank you @ekristen 🍻🍻🍻! |
Recently I started creating IOT authorizers in my AWS acc, and once I run AWS Nuke, it is unable to delete them for some reason. 🤔
The AWS Nuke version I'm using is:
Maybe it's related to the fact that, at least from the UI, you first need to deactivate an authorizer, and then delete it? 🤔
In any case, if anybody has any clue, it'd be helpful. I can also provide extra logs if needed. Just let me know!
The text was updated successfully, but these errors were encountered: