You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "squakez (via GitHub)" <gi...@apache.org> on 2026/08/25 13:09:30 UTC
[I] Deprecate user building features [camel-k]
squakez opened a new issue, #6775:
URL: https://github.com/apache/camel-k/issues/6775
### Requirement
As we're providing feature parity between `IntegrationProfile` and the old `IntegrationPlatform` (#6705) we should remove the following features:
- builder trait: move builder properties to camel trait instead
- integration repositories: only inherit those available in the profile.
We must introduce a deprecation notice to enable future removal. We want to only enable certain build features via an administrative role (for example, via the creation of profiles).
Beside those we should enable the following policies in the profile (and default env var):
- enable Quarkus native: to make this option available via profile only
- quarkus images to use: use only the one provided in the profile (via allowlist)
- base images: use only the one provided in the profile (via allowlist)
--
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-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Deprecate user building features [camel-k]
Posted by "ansh0014 (via GitHub) via commits" <co...@camel.apache.org>.
ansh0014 commented on issue #6775:
URL: https://github.com/apache/camel-k/issues/6775#issuecomment-6690567789
hey@squakez!
I want explore to this issue and understand the internal design involved. Would it be okay if I spend some time looking into it and thinking through a possible approach?
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Deprecate user building features [camel-k]
Posted by "squakez (via GitHub) via commits" <co...@camel.apache.org>.
squakez commented on issue #6775:
URL: https://github.com/apache/camel-k/issues/6775#issuecomment-6704249466
> hey@squakez! I want explore to this issue and understand the internal design involved. Would it be okay if I spend some time looking into it and thinking through a possible approach?
Thanks for the interest. I think this need before some design change that is in scope within v3 and some development that is still ongoing. Still early to tackle at this point.
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Deprecate user building features [camel-k]
Posted by "Thundercloud12 (via GitHub)" <gi...@apache.org>.
Thundercloud12 commented on issue #6775:
URL: https://github.com/apache/camel-k/issues/6775#issuecomment-6084972297
yes i would considering the back and forth we did on artemis queue, okay so the design now:
Our goal is to centralise the config, allowing less access to the developers to roughly sum it up,implementation can be done as follows:
1. Move the buildertrait up to the camel so that only admin would be able to define them
2. for maven repository centralise it in integrationprofile
3. Quarkus native build policy: Introduce a configurable policy through IntegrationProfile and QUARKUS_NATIVE_ENABLED to control whether native builds are permitted
4. -Shared allowlist architecture: Reuse common configuration parsing and validation utilities for Maven repositories, Quarkus images, and build base images, while maintaining separate resource-specific policies.
5.Image validation: Validate nativeBaseImage, nativeBuilderImage, and builder.baseImage against the effective platform configuration and applicable allowlists. Reject unauthorized images
this pattern of validating against a list provided by lets say admin is common i would like to implement it common across all of them where it is useful like macen and that image build settings
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Deprecate user building features [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #6775:
URL: https://github.com/apache/camel-k/issues/6775#issuecomment-6146585539
Okey, thanks for the analysis effort. I realize this is requiring a bit of more internal design changes, so it needs some more experience to have a deeper internal knowledge. It's not marked as `good-first-issue` for this reason and it is better that any more knowledge committer takes care. I'll remove the assignment if you don't mind and feel free to pick up any other open issue.
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Deprecate user building features [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #6775:
URL: https://github.com/apache/camel-k/issues/6775#issuecomment-6076012477
@Thundercloud12 sure, thanks! Feel free to provide a short low level design first so we can have a discussion about the directions to take before the implementation if you prefer.
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Deprecate user building features [camel-k]
Posted by "Thundercloud12 (via GitHub)" <gi...@apache.org>.
Thundercloud12 commented on issue #6775:
URL: https://github.com/apache/camel-k/issues/6775#issuecomment-6064357044
@squakez i am taking this up if it is okay with you!
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org