[GitHub] [camel-k] nicolaferraro opened a new issue #1135: Basic module structure for Camel K projects

[GitBox <gi...@apache.org>]

nicolaferraro opened a new issue #1135: Basic module structure for Camel K projects
URL: https://github.com/apache/camel-k/issues/1135
 
 
   Going forward version 1.0.0 we should think about how people will organize complex integrations that they will run in production. We strongly want to keep a single file model for the integrations, but often you need to provide resources, like:
   - Properties
   - API definitions
   - Transformation and mapping files
   - Test files (yet to come)
   
   That means that even in a simple project composed of few integrations that interact together, it will be difficult to understand what resources belong to what integration.
   
   E.g. When you have multiple integrations, which one does an `application.properties` file refer to?
   
   We need to define some module structure for integrations. It may be something encoded in the `kamel` CLI (e.g. `kamel scaffold name`) or simply a best practice we propose also in the examples.
   
   The simplest model I can imagine is creating as less structure as possible, keeping a minimum of visual order in a project.
   
   e.g.
   ```
   module1
     module1integration.groovy
     application.properties
     trasnform.xslt
   
   module2
     tests
       moduletest.feature
       moduletest2.feature
       moduletest3.feature
     module2integration1.groovy
     module2integration2.groovy
     application.properties
     README.md
   
   rootmoduleintegration.groovy
   ```
   
   Questions:
   - Is that the best structure we can have for integrations?
   - Should we provide some tools to scaffold it (e.g. create the basic quickstart)?
   - Should we provide some tools in the CLI to run a module?
   - Should we define a module configuration (as in the comments #1133)
   - Other ideas?
   
   @lburgazzoli , @davsclaus, @astefanutti , @jamesnetherton, @valdar, @oscerd 

----------------------------------------------------------------
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