Seeding fails when ruleset.yaml does not exist.

[jortel]

Seeding fails when ruleset.yaml does not exist. I think it's only used for RuleSet.Name and RuleSet.Description which can be derived from the parent directory.

time=2025-04-29T15:01:23Z level=info msg=[seeding] Applying seeds.
time=2025-04-29T15:01:24Z level=error msg=[hub] open /tmp/seed/rulesets/spring-boot/ruleset.yaml: no such file or directory
github.com/konveyor/tackle2-seed/pkg.(*RuleSet).readRuleSet()
	/opt/app-root/pkg/mod/github.com/konveyor/tackle2-seed@v0.0.0-20231025181853-8ce94f70f744/pkg/ruleset.go:90
github.com/konveyor/tackle2-seed/pkg.(*RuleSet).Load()
	/opt/app-root/pkg/mod/github.com/konveyor/tackle2-seed@v0.0.0-20231025181853-8ce94f70f744/pkg/ruleset.go:67
github.com/konveyor/tackle2-seed/pkg.(*Seed).DecodeItems()
	/opt/app-root/pkg/mod/github.com/konveyor/tackle2-seed@v0.0.0-20231025181853-8ce94f70f744/pkg/seed.go:78
github.com/konveyor/tackle2-hub/seed.(*RuleSet).With()
	/opt/app-root/src/seed/ruleset.go:24
github.com/konveyor/tackle2-hub/seed.(*Hub).With()
	/opt/app-root/src/seed/seed.go:31
github.com/konveyor/tackle2-hub/seed.Seed()
	/opt/app-root/src/seed/pkg.go:75
main.Setup()
	/opt/app-root/src/cmd/main.go:49
main.main()
	/opt/app-root/src/cmd/main.go:107
runtime.main()
	/usr/lib/golang/src/runtime/proc.go:271
runtime.goexit()
	/usr/lib/golang/src/runtime/asm_amd64.s:1695
panic: open /tmp/seed/rulesets/spring-boot/ruleset.yaml: no such file or directory

[konveyor-ci-bot]

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

[aufi]

Good point, this missing yaml file was added last week - https://github.com/konveyor/rulesets/blob/main/default/generated/spring-boot/ruleset.yaml, I expecrienced the same error before.

My preference would be to fail more gracefully if ruleset.yaml file is missing or validate rulesets before seeding, but that's just my suggestion. This might be relevant for @jmle too.