How to validate cluster.yaml?

[tisonkun]

I got:

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

goroutine 447 [running]:
github.com/weaveworks/eksctl/pkg/cfn/builder.convertConfiguration(0x140004c1f48)
	github.com/weaveworks/eksctl/pkg/cfn/builder/capability.go:104 +0xe8
github.com/weaveworks/eksctl/pkg/cfn/builder.(*CapabilityResourceSet).AddAllResources(0x14000a90000)
	github.com/weaveworks/eksctl/pkg/cfn/builder/capability.go:45 +0x238
github.com/weaveworks/eksctl/pkg/actions/capability.(*Creator).createCapabilityStack(0x140009e30c0, {0x1063f34c0, 0x108b52a40}, 0x14000ab8280)
	github.com/weaveworks/eksctl/pkg/actions/capability/creator.go:122 +0x2b0
github.com/weaveworks/eksctl/pkg/actions/capability.(*Creator).createCapability(0x140009e30c0, {0x1063f34c0, 0x108b52a40}, 0x14000ab8280)
	github.com/weaveworks/eksctl/pkg/actions/capability/creator.go:103 +0x30
github.com/weaveworks/eksctl/pkg/actions/capability.(*Creator).CreateTasks.func1()
	github.com/weaveworks/eksctl/pkg/actions/capability/creator.go:80 +0xa4
github.com/weaveworks/eksctl/pkg/utils/tasks.(*GenericTask).Do(0x14000a29020, 0x0?)
	github.com/weaveworks/eksctl/pkg/utils/tasks/tasks.go:31 +0x34
github.com/weaveworks/eksctl/pkg/utils/tasks.doSingleTask(0x14000cd4b60, {0x10638db38, 0x14000a29020})
	github.com/weaveworks/eksctl/pkg/utils/tasks/tasks.go:202 +0xc0
github.com/weaveworks/eksctl/pkg/utils/tasks.doParallelTasks.func1(0x14000bc8c40?)
	github.com/weaveworks/eksctl/pkg/utils/tasks/tasks.go:220 +0x70
created by github.com/weaveworks/eksctl/pkg/utils/tasks.doParallelTasks in goroutine 446
	github.com/weaveworks/eksctl/pkg/utils/tasks/tasks.go:218 +0x58

This is because I have a typo in the cluster.yaml when running eksctl create cluster -f cluster.yaml. That is, awsIdc typo as awsIDC.

I'd like to know if there is any way to do the validations?

[github-actions]

Hello tisonkun 👋 Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website

[NicholasBlaskey]

I believe this is part of this known issue where our parsing library gets confused on case sensitive yaml keys
#753

To fix this we will need to likely use a different parsing library or run another json schema validation check