feat: Set log level of a specific package using logging trait

[realMartinez]

• added capability to the logging trait to set log level of user specified package
• added unit test

Usage:
-t "logging.category.'org.test'=DEBUG"

Release Note

feat: Set log level of a specific package using logging trait

[realMartinez]

(OLD)feat: Set log level of a specific package using logging trait

[squakez]

This check is more suitable of a unit test, like it already exists. E2E test should check that the configuration is applied correctly, ie, checking Pod's env variables and above all, checking the log traces exposed have that DEBUG level.
As an example, see how we check for content in this test:

camel-k/e2e/common/languages/java_test.go

Line 43 in b86a7fb

Eventually(IntegrationLogs(ns, "java"), TestTimeoutShort).Should(ContainSubstring("Magicstring!"))

[github-actions]

⚠️ Unit test coverage report - coverage decreased from 36.8% to 36.4% (-0.4%)

[claudio4j]

I tried to run as ./kamel run --name javava e2e/common/traits/files/Java.java -t "logging.category.'org.apache.camel.impl'=DEBUG"

But it fails in the camel-k-operator, the log says "logger":"KubeAPIWarningLogger","msg":"unknown field \"status.traits.logging.category\""}

Then the integration status keeps changing from Initialization to Building Kit and back to initialization.

This is because the Integration CRD is missing the new category field, to fix it you should run make generate and amend the change to the commit.

[claudio4j]

Also, trying the -t "logging.category.'org.apache.camel.impl'=DEBUG", there were no DEBUG level log in the integration pod.
The quarkus logging documentation about categories, when used with environment variables, the category name should be surround by two underscores, example: QUARKUS_LOG_CATEGORY__ORG_APACHE_CAMEL__LEVEL=DEBUG

That's why there is no DEBUG level log messages in the integration log.

quarkus logging shorts the log category name, the org.apache.camel. can be shortened to org.apa.cam., see an example:

DEBUG [org.apa.cam.sup.LRUCacheFactory] (main) Creating DefaultLRUCacheFactory

The test should monitor for this type of log content. The same for the org.jboss category.