-
Notifications
You must be signed in to change notification settings - Fork 202
Allow deep configuration for enrichers #1375
Comments
What I can see is that in So the problem is that The problem is that these parameters are not simply exposed by So my idea would be that all these Maven types ( What do you think about this approach? Or you have other thing in mind? |
@rhuss You reopened this issue to improve how we can pass the custom configuration to an enricher. We didn't talk about but what could be this improvement. Do you have for example something in mind like an xpath for objects, so you say I want to attribute as |
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions! |
Description
Currently only flat configuration is supported by default (i.e. a simple key-value map). However, there are already enrichers (e.g. the
VertxHealthCheckEnricher
) which examines the plugin configuration on is own by parsing the XML. However those enrichers are tightly coupled to maven and can't easily reused outside a Maven context.This should not be required, but the enrichers should support nested configurations by default, which actually should be a plain map of maps with plain string values (could also contain lists).
The text was updated successfully, but these errors were encountered: