kudobuilder / kudobuilder/kitt
Old Operators can not be added because of too strict validation
- Dominant language
- Go
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Tried to add kafka operator 1.2.0 - It didn't work because the validator runs too many strict checks.
Additionally, when we add new validations in KUDO it might happen that existing entries in the index do not pass these new validations - the should still be added to the index on a rebuild.
So we need either a "skipValidation" or "validationLevel" or "kudoValidationVersion" that can execute the KUDO package validation with the correct KUDO version...
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the KUDO package validation performed while rebuilding the index, then reproduce the failure with Kafka operator 1.2.0. Determine how validation should account for the KUDO version or existing index entries, and define done as successfully adding older operators without weakening appropriate validation for new entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100