From 6959228c5c557df0204a2902807b35d90063b600 Mon Sep 17 00:00:00 2001 From: Christof Rabensteiner Date: Wed, 15 May 2019 14:55:09 +0200 Subject: Handle Config Related Edge Cases in Augmenter & ProfileGenerator ConfigProfileGenerator: - Cancel startup if default Config profile is incomplete. - Add property flag 'verify-completeness-of-default-delivery-request-configuration', which allows admin to disable completeness check. In that case, just log a warning if the default profile is incomplete. Augmenter: - Ensure that after merging the config is complete (or throw an exception otherwise). - Refactor: Move ConfigProfileValidator from ConfigProfileGenerator to dedicated "ConfigProfileValidator" class; Reason: Augmenter needs to check completness of at-runtime-compiled configuration. - Refactor: Rewrote code for better readability. Others - NPE Fix in ConfigProfileMerger: If FallbackConfigProfile/Server is empty, use PrimaryProfile/Server. --- src/main/resources/application.yaml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'src/main/resources') diff --git a/src/main/resources/application.yaml b/src/main/resources/application.yaml index 98987b8..9e987bf 100644 --- a/src/main/resources/application.yaml +++ b/src/main/resources/application.yaml @@ -25,4 +25,9 @@ delivery-request-configuration-profiles: app-profile-2: msg: - url: https://msg-url2.com \ No newline at end of file + url: https://msg-url2.com + +## If set to false, moa zs ignores an incomplete default DeliveryRequest-configuration +## profile and continues startup. See 'delivery-request-configuration-profiles'. +## Default value: true +# verify-completeness-of-default-delivery-request-configuration: false \ No newline at end of file -- cgit v1.2.3