SnehaNprog commented on issue #6939:
URL: https://github.com/apache/camel-k/issues/6939#issuecomment-6837496296
Building on what @knockknock10 mentioned, if we keep modelines, I think the
separation between `build` and `deploy` introduces an interesting question
around how configuration is handed off.
Currently, modelines can contain both build-time configuration
(dependencies, build traits) and deployment-time configuration (container
traits, mounts, replicas).
With separate commands, how would we handle that boundary?
Should `kamel build` resolve the configuration and produce a
deployment-ready manifest alongside the image?
Or should `kamel deploy` still parse the original integration source to
extract deployment-specific configuration?
I wonder if having `build` produce a resolved declarative artifact would
make the workflow cleaner, especially for CI/CD and GitOps use cases, without
coupling deployment back to source parsing.
Intrested in discussion just wanted to add my thoughts
--
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]
