marteloudini commented on issue #91: URL: https://github.com/apache/camel-k-examples/issues/91#issuecomment-3345196099
We will manage everything using GitOps (private repository). 1) Git repository for entities and business logic (developed exclusively by the business teams): simple POJO classes, built with Maven and packaged as JAR files. The Integration Team will: 1) Convert existing routes to Camel-K. 2) Maintain the Git repository for Camel route definitions (YAML files, using Kustomize). 3) Manage the ArgoCD Git repository (for deployment, promoting changes from dev to test to QA to production). I want to implement a "clean architecture". The Camel-K routes, or "pipes," will retrieve entity data and business transformation logic from JitPack. This way, the routes can use these resources within their own container. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
