-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Prevent operator panic on wrong Kamelet binding #3595
Conversation
1279535
to
87e1f90
Compare
87e1f90
to
cd1b08d
Compare
The builds are failing due to:
Both are not related to these changes |
cd1b08d
to
dbed12a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the work. This PR solves certain specific cases (ie, a sink with a not nil
endpoint), but still fails in case of a valid yaml specification that does not fit the expected ErrorHandler
specification. A definitive fix should be done in the parseErrorHandler
func, when we unmarshal the configuration. Not sure if there is an easy and elegant way to validate against the expected schema. In any case, I'd keep this work on hold, as we may need to apply some refactoring due to apache/camel-k-runtime#868
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As Pasquale said, let's leave it open for now.
Ok no problem once apache/camel-k-runtime#868 will be fixed, I will try to find a more elegant approach |
fixes #3586
Motivation
A Kamelet binding in the wrong format can lead to operator panic which needs to be avoided.
Modifications:
Release Note