Seg fault processing a Deployment

[viniciusmucuge]

Trying to helmify some manifests I have the following segmentation fault code:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1691f93]

goroutine 1 [running]:
github.com/arttor/helmify/pkg/processor/deployment.deployment.Process({}, {0x1906678, 0xc0000aed40}, 0xc00000e548)
	/home/runner/work/helmify/helmify/pkg/processor/deployment/deployment.go:71 +0x293
github.com/arttor/helmify/pkg/app.(*appContext).process(0xc0000e9d50, 0xc00000e548)
	/home/runner/work/helmify/helmify/pkg/app/context.go:75 +0x39c
github.com/arttor/helmify/pkg/app.(*appContext).CreateHelm(0xc0000e9d50, 0xc000308000)
	/home/runner/work/helmify/helmify/pkg/app/context.go:57 +0x252
github.com/arttor/helmify/pkg/app.Start({0x18f4d20, 0xc00000e010}, {{0x7ffeefbffa88, 0xc}, {0x17ee766, 0x1}, 0x0, 0x0})
	/home/runner/work/helmify/helmify/pkg/app/app.go:58 +0x737
main.main()
	/home/runner/work/helmify/helmify/cmd/helmify/main.go:21 +0x1b1

Someone had a similar situation?

[arttor]

@viniciusmucuge i found the problem. There is no check if deployment spec.replicas is missing. I will create a fix and release. As a workaround, you can set some value to spec.replicas in deployment.yaml.

[arttor]

@viniciusmucuge fixed in v0.3.3 release

[viniciusmucuge]

Thanks a lot @arttor
After upgrading to v0.3.3, worked correctly