-
Task
-
Resolution: Done
-
Major
-
camel-k-1.6.1
-
None
-
integration-doc-2022-01-17, integration-doc-2022-02-07, integration-doc-2022-02-28, integration-doc-2022-03-21, integration-doc-2022-04-11, integration-doc-2022-05-02, integration-doc-2022-05-23
From Pasquale in email message:
Hi Melissa and Bruno,
recently I'm working on removing deprecated code from Camel K project base and I realized we missed to make an important update both upstream and downstream. It's about the usage of `.kamelet.spec.flow` parameter that has been deprecated since a while in favor of `.kamelet.spec.template` parameter.
I'm working to fix all the documentation, examples and kamelets definitions upstream, but we need to update accordingly in product documentation. Ideally this should be performed in next releases, so, whenever we remove the deprecated field from the API, there won't be need of any additional work. Most importantly, our users will be aware of the change in the definition and won't be surprised by the future removal.
Do you think is it feasible handling this in 1.6.4 already? It is about spotting all the definition and substituting.
https://github.com/apache/camel-kamelets/commit/2cbe1fd8df3485623f213384eac11f454b533fb6
- is related to
-
ENTESB-18389 Kamelet Catalog to use .spec.template vs .spec.flow
- Closed