painbaba opened a new pull request, #6951: URL: https://github.com/apache/camel-k/pull/6951
Closes #6948. ## What Completes the IntegrationProfile e2e coverage in `e2e/common/misc/integration_profile_test.go` (until now only the annotation-selected profile was exercised, via a dependencies-only scenario): - **TestIntegrationProfileProperties** — an IntegrationProfile selected through the `camel.apache.org/integration-profile.id` annotation applies its traits: the `camel.properties` trait value is asserted on the running Integration's log - **TestIntegrationProfileFromNamespaceAnnotation** — an Integration with no explicit annotation picks up the profile selected by the same annotation on its namespace - **TestIntegrationProfileDefault** — with neither annotation set, the `default` IntegrationProfile in the namespace applies - the pre-existing dependencies-propagation scenario (**TestIntegrationProfileDependencies**) is kept verbatim, so profile dependencies stay covered alongside the new trait scenarios - new fixture `e2e/common/misc/files/profile-property.yaml` (timer -> log, body reads `properties:profile.property`) ## Validation - `go vet -tags=integration ./e2e/common/misc/...` passes locally - the e2e scenarios themselves execute on a Kubernetes cluster only and were **not** run locally — they will be exercised by the project's e2e CI ## Disclosure This contribution is 100% AI-generated and AI-tested — Z.ai GLM-5.3-Flash via AutoClaw. Nobody hand-wrote or hand-reviewed these lines; the local verification is exactly `go vet` as stated above, and the cluster-executed assertions are left to the project's CI. -- 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]
