nicolaferraro opened a new issue #1590: URL: https://github.com/apache/camel-k/issues/1590
I've seen now this commit @astefanutti : https://github.com/apache/camel-k/commit/1b95c5a2b19c8566860fff0b2b736a0b8b8470a3 The flow type was "special" meaning that it allowed to create an integration like: ``` kind: Integration apiVersion: camel.apache.org/v1 spec: flows: - from: uri: timer steps: - log: message: Hello ``` While, setting it as string the integration becomes "probably" like: ``` kind: Integration apiVersion: camel.apache.org/v1 spec: flows: - |- from: uri: timer steps: - log: message: Hello ``` I don't think we have e2e tests (but we should add them). In terms of JSONSchema, it was an array of objects, now it's an array of strings. The reason why this was important is because the Integration object was a unique YAML (also convertible to json) and when @lburgazzoli completes the YAML schema for validation, also the integration object can have autocompletion/verification by tooling.. And that is also more important for Kamelets.. Does the conversion to string affect everything as I've described @astefanutti ? ---------------------------------------------------------------- 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: [email protected]
