nicolaferraro opened a new issue #730: Allow backward compatible changes in CRD URL: https://github.com/apache/camel-k/issues/730 Let's consider the following scenario. I have a knative controller that reads and write camel K integrations. It imports the camel k apis, version 0.3.3. After some point in time we release 0.4.0 with an additional field "version". Technically the knative controller can ignore that field, but in practice it can't, because the kubernetes unmarshalling fails when mapping the integration json into the 0.3.3 structs (that miss the "version" field). Everything would be easier if we ignore unknown properties by default, by sending them into a "unknownFields" map struct during unmarshalling. This would make the handshake between a super controller and camel k integrations easier, because the super-controller can depend on camel k version 0.4.x+ and not a precise version. Versioning the resources does not help.
---------------------------------------------------------------- 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] With regards, Apache Git Services
