[9.2] (backport #11619) Add default option to allow merging multiple agent config keys #11634
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Merge multiple
agent.*keys when handling config.Why is it important?
Multiple keys were getting silently ignored, leading to configs that contain:
not working as expected.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration files./changelog/fragmentsusing the changelog toolI have added an integration test or an E2E testDisruptive User Impact
Standalone agent configs will no longer silently ignore multiple
agent.*attributes.How to test this PR locally
Create a stand-alone config with multiple
agent.*entries such as:and observe that the logging entries are configured correctly.
Related issues
This is an automatic backport of pull request Add default option to allow merging multiple agent config keys #11619 done by Mergify.