aws-nuke
aws-nuke copied to clipboard
Go panic when reaching route53resolverrule during dry run.
Version: aws-nuke-v2.17.0
us-east-1 - Route53ResolverRule - rslvr-autodefined-rr-internet-resolver (Internet Resolver) - [ID: "rslvr-autodefined-rr-internet-resolver", Name: "Internet Resolver"] - Filtering DomainName "." us-east-1 - Route53ResolverRule - panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x103c5acf0]
goroutine 1 [running]: github.com/rebuy-de/aws-nuke/resources.(*Route53ResolverRule).String(0x140009a7440, 0x105aff918, 0x140009a7440) /home/runner/work/aws-nuke/aws-nuke/resources/route53-resolver-rules.go:139 +0x60 github.com/rebuy-de/aws-nuke/cmd.Log(0x14000c69740, 0x103d0bb59, 0x13, 0x105aff918, 0x140009a7440, 0x1400011b1c8, 0x1, 0x1, 0x0, 0x103cf29a0, ...) /home/runner/work/aws-nuke/aws-nuke/cmd/log.go:51 +0x2d4 github.com/rebuy-de/aws-nuke/cmd.(*Item).Print(0x140009a7740) /home/runner/work/aws-nuke/aws-nuke/cmd/queue.go:36 +0x1a4 github.com/rebuy-de/aws-nuke/cmd.(*Nuke).Scan(0x1400054e000, 0xd, 0x0) /home/runner/work/aws-nuke/aws-nuke/cmd/nuke.go:173 +0x2d0 github.com/rebuy-de/aws-nuke/cmd.(*Nuke).Run(0x1400054e000, 0x1400054e000, 0x0) /home/runner/work/aws-nuke/aws-nuke/cmd/nuke.go:61 +0x2d0 github.com/rebuy-de/aws-nuke/cmd.NewRootCommand.func2(0x1400032cf00, 0x14000141120, 0x0, 0x2, 0x0, 0x0) /home/runner/work/aws-nuke/aws-nuke/cmd/root.go:90 +0x2d8 github.com/spf13/cobra.(*Command).execute(0x1400032cf00, 0x140001140a0, 0x2, 0x2, 0x1400032cf00, 0x140001140a0) /home/runner/work/aws-nuke/aws-nuke/vendor/github.com/spf13/cobra/command.go:852 +0x320 github.com/spf13/cobra.(*Command).ExecuteC(0x1400032cf00, 0x10102417c, 0x1045cf0e0, 0x14000000180) /home/runner/work/aws-nuke/aws-nuke/vendor/github.com/spf13/cobra/command.go:960 +0x258 github.com/spf13/cobra.(*Command).Execute(...) /home/runner/work/aws-nuke/aws-nuke/vendor/github.com/spf13/cobra/command.go:897 main.main() /home/runner/work/aws-nuke/aws-nuke/main.go:25 +0x24
Hello @hugorodro.
I'm wondering if you were able to bypass this somehow?
Tom
I'm getting the same issue with version 2.25.0