You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@camel.apache.org by GitBox <gi...@apache.org> on 2019/06/26 15:14:23 UTC

[GitHub] [camel-k] nicolaferraro opened a new issue #778: Handle defaults differently (aka do not change specs)

nicolaferraro opened a new issue #778: Handle defaults differently (aka do not change specs)
URL: https://github.com/apache/camel-k/issues/778
 
 
   I'm working on upgrades and I think we have a issue with defaults.
   
   We use the integrationplatform as global config location and if a property is not set on the platform, we set its default value in the spec during the "initialize" phase.
   
   E.g. when initializing a empty integrationplatform we set runtimeVersion to 0.3.3
   
   But if we upgrade Camel K to a version that uses runtimeVersion 1.0.0 by default, we can't tell if that 0.3.3 was set by the user or was a default value added by the previous release.
   
   We should compute defaults without writing them into the spec field.
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services