squakez commented on pull request #2635: URL: https://github.com/apache/camel-k/pull/2635#issuecomment-920664604
> I wonder what do you see should be added as parameters to that new _configuration_ trait? In the immediate term, we should have `properties`, `resources` and `config` (which logic is actually behind `kamel run --p/--resource/--config`). > I'm asking just to understand what responsibilities should be captured by that new trait, as configuration is a very general concept. So I wonder, if that's going to be application properties and resources, maybe a new _runtime_ trait may be the right abstraction that we are trying to capture, as we have other traits, like _camel_, builder_, _deployer_, _platform_ (pretty much every trait) that "configure" things to some extend. I don't have a strong opinion on the name to adopt here. The original discussion was born when we started the [refactoring of the user properties and configuration](https://github.com/apache/camel-k/issues/2003#issuecomment-843874243). Considering that the idea is also to replace `.spec.configuration` I felt it was consistent, although very generic name. -- 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. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
