nicolaferraro commented on pull request #1602: URL: https://github.com/apache/camel-k/pull/1602#issuecomment-671872611
> Thinking a little bit more, we can get rid of the schema as loading it is heavy and we only need to know the list of properties the kamelet supports, like: > > ``` > camel.k.sources[0].name = timer > camel.k.sources[0].language = yaml > camel.k.sources[0].location = file:/etc/camel/sources/timer/timer.yaml > camel.k.sources[0].type = template > camel.k.sources[0].properties-names[0] = a > camel.k.sources[0].properties-names[1] = b > camel.k.sources[0].properties-names[2] = c > ``` > > or > > ``` > camel.k.sources[0].name = timer > camel.k.sources[0].language = yaml > camel.k.sources[0].location = file:/etc/camel/sources/timer/timer.yaml > camel.k.sources[0].type = template > camel.k.sources[0].properties-names = a,b,c > ``` > > then if any of the property has a default value, that value can be added to the list of initial properties so assuming the property `a` has a default value of `foo`, then the operator should generate a property like: > > ``` > camel.kamelet.timer.a = foo > ``` Can we do one of the two also for standard sources? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
