CAMEL-21484: mp-config should not be loadable as it has overhead at r…

[davsclaus]

…untime

Description

Target

• I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

• If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• I checked that each commit in the pull request has a meaningful subject line and body.

• I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟

🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run

• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot.

• You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.

• Build and test logs are available in the Summary page. Only Apache Camel committers have access to the summary.

• ⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[Paul-Blanchaert]

@davsclaus
I believe we still require the method isValidForActiveProfiles(String name). This filters the "active" properties for the selected runtime profile(s). That might be the reason why the "loadable" was chosen in the first place.
CAMEL-21480 is expected to enhance this isValidForActiveProfiles(String name) method to support for multiple profiles.

[Paul-Blanchaert]

On 2nd thought: probably that CAMEL-21480 is also sorted by using the service as it delegates that function to the service...
Can we add some tests to validate that? I'm happy to help with that.

[jamesnetherton]

I believe we still require the method isValidForActiveProfiles(String name). This filters the "active" properties for the selected runtime profile(s

I don't think that's needed with this change. If we're just resolving properties at runtime via ConfigProvider, then it'll factor in whatever active profiles are enabled.