Errors unrelated to nuking cause exit status 1. about aws-nuke HOT 9 CLOSED

@YuriGal thanks, on it.

from aws-nuke.

@YuriGal this is probably why the original nuke doesn't support global filters. How would you like this to behave? Simply warn that it doesn't support it? This could cause filters to be ignored completely. Especially ones defined globally is that acceptable?

from aws-nuke.

Actually I found the problem. You are right the original nuke just allowed it to continue and logged an warning. I will fix this regression and push an update.

from aws-nuke.

Thanks!

from aws-nuke.

This should be fixed on the latest beta release https://github.com/ekristen/aws-nuke/releases/tag/v3.0.0-beta.19

from aws-nuke.

@YuriGal just calling direct attention here so you see it. Thanks for the testing and feedback.

from aws-nuke.

Hi, sorry for the delay, just tried beta.19 - and it works! What's interesting, that list of log errors is much longer now, it shows errors it didn't show before. But it completes successfully.

from aws-nuke.

No worries on delay. Just wanted to make sure you saw the update. Again appreciate the feedback.

There were errors not previously logged or hidden in the past. I rewrote then underlying library and improved logging across the board.

Feel free to share your output sanitized or you can email me direct at [email protected]

I can review to see if there's room to improve or if there's specific things you are seeing that look off please let me know.

from aws-nuke.

🎉 This issue has been resolved in version 3.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

from aws-nuke.