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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
