How does many optional options design when use camel components in kamelets

[wingerx]

Hey,
Could anyone help me?
I created Kameletbinding for DBZ component by kamelets developer guide.But i want to configure only the required options, and the optional options are filled in as needed in kamelets binding yaml file. There are so many options for DBZ, and it is not conducive to subsequent expansion if all are defined.
There is an additionalProperties option in DBZ components, but I don’t know how to configure it in yaml and make it take effect.

Any ideas?

[oscerd]

You need to think to Kamelets as pre-baked actions, so there are no means in having all the possibile options available as parameters in the kamelet.

[wingerx]

I'm sorry,i don't understand.
Can you explain this for me please?

[oscerd]

In camel component you have multiple parameters to tune your route and set everything. A Kamelet needs to define just a subset of the options to perform a pre-defined operation. So in a Kamelet you'll never see all the possible options listed and configurabile, because in terms of Kamelets this is conceptually wrong.

[wingerx]

ok, I see.
Thanks a lot. @oscerd