Fixing a null pointer exception in Route53ResolverRule

[sinisa229]

When we are running nuke, we get the following error:

goroutine 1 [running]:
--
690 | github.com/rebuy-de/aws-nuke/v2/resources.(*Route53ResolverRule).Filter(0xc002339430?)
691 | /src/resources/route53-resolver-rules.go:103 +0x12
692 | github.com/rebuy-de/aws-nuke/v2/cmd.(*Nuke).Filter(0xc0003c8840, 0xc0013afcc0)
693 | /src/cmd/nuke.go:196 +0x53
694 | github.com/rebuy-de/aws-nuke/v2/cmd.(*Nuke).Scan(0xc0003c8840)
695 | /src/cmd/nuke.go:173 +0x9cb
696 | github.com/rebuy-de/aws-nuke/v2/cmd.(*Nuke).Run(0xc0003c8840)
697 | /src/cmd/nuke.go:61 +0x325
698 | github.com/rebuy-de/aws-nuke/v2/cmd.NewRootCommand.func2(0xc00034e800?, {0x5843b0d?, 0x4?, 0x5843b11?})
699 | /src/cmd/root.go:92 +0x613
700 | github.com/spf13/cobra.(*Command).execute(0xc0002c8300, {0xc0000b4010, 0xb, 0xb})
701 | /src/vendor/github.com/spf13/cobra/command.go:940 +0x87c
702 | github.com/spf13/cobra.(*Command).ExecuteC(0xc0002c8300)
703 | /src/vendor/github.com/spf13/cobra/command.go:1068 +0x3a5
704 | github.com/spf13/cobra.(*Command).Execute(0xc0000061a0?)
705 | /src/vendor/github.com/spf13/cobra/command.go:992 +0x13
706 | main.main()
707 | /src/main.go:10 +0x18
708 |  
709 | [Container] 2023/10/25 23:04:14.209271 Command did not exit successfully bin/destroy --no-dry-run --force exit status 2
710 | [Container] 2023/10/25 23:04:14.212499 Phase complete: BUILD State: FAILED

This doesn't happen for all regions. It happens for us-east-1.

[mtovino-nefeli]

I've observed the same error, thank you for the fix!

[bassjompi]

Im having the same issue, thanks a lot for the fix. Hope its merged soon

[SSKale1]

Faced a similar issue, thanks for the fix, also faced issues in other regions. (me-south-1, ap-southeast-1)

[kurtmc]

This issue affects us too. Keen to see this get merged.

[tmax22]

whats going on guys? i can see the issue is still open but this related pr was not merged upstream. i got the exact same issue (same error and error trace) on aws nuker v2.25.0. is it possible to merge?

[der-eismann]

Hey everyone, please see the readme of the project for an updated status:

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.
We appreciate all the support and contributions we've received throughout the life of this project. We believe that the fork will continue to provide the functionality and support that you have come to expect from aws-nuke.
Please note that this deprecation means we will not be addressing issues, accepting pull requests, or making future releases from this repository.
Thank you for your understanding and support.

[ekristen]

@sinisa229 this issues has been fixed via ekristen/aws-nuke#15 and ekristen/aws-nuke#287.

@tmax22 looks like you had/have approval authority on this repository. If you are interested in continuing to contribute and review, please reach out!

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.
We appreciate all the support and contributions we've received throughout the life of this project. We believe that the fork will continue to provide the functionality and support that you have come to expect from aws-nuke.
Please note that this deprecation means we will not be addressing issues, accepting pull requests, or making future releases from this repository.
Thank you for your understanding and support.

[tmax22]

@ekristen I have no idea why I have approval authority on this repo. Most probably everyone one have.
Thank you for your awesome work!