This bug is became apparent during the security update process.
It seems that the mp-client configurations are not correctly passed from the root config (restructure.yaml) to the lower level configuration classes (FormattedPathFactory.kt in particular).
java.lang.IllegalArgumentException: Cannot configure MorePathFactory without auth.managementPortalUrl under path.properties
at nl.chdr.morecloud.output.path.MorePathFactory$Plugin.<init>(MorePathFactory.kt:41) ~[more-output-restructure-0.2.1.jar:0.2.1]
at nl.chdr.morecloud.output.path.MorePathFactory.create(MorePathFactory.kt:27) ~[more-output-restructure-0.2.1.jar:0.2.1]
at org.radarbase.output.path.PathFormatterPluginKt.toPathFormatterPlugin(PathFormatterPlugin.kt:29) ~[radar-output-restructure-2.3.3-SNAPSHOT.jar:unspecified]
at org.radarbase.output.path.PathFormatterPluginKt$toPathFormatterPlugins$2.invoke(PathFormatterPlugin.kt:13) ~[radar-output-restructure-2.3.3-SNAPSHOT.jar:unspecified]
at org.radarbase.output.path.PathFormatterPluginKt$toPathFormatterPlugins$2.invoke(PathFormatterPlugin.kt:13) ~[radar-output-restructure-2.3.3-SNAPSHOT.jar:unspecified]
at kotlin.sequences.TransformingSequence$iterator$1.next(Sequences.kt:210) ~[kotlin-stdlib-1.9.21.jar:1.9.21-release-633]
at kotlin.sequences.FilteringSequence$iterator$1.calcNext(Sequences.kt:170) ~[kotlin-stdlib-1.9.21.jar:1.9.21-release-633]
at kotlin.sequences.FilteringSequence$iterator$1.hasNext(Sequences.kt:194) ~[kotlin-stdlib-1.9.21.jar:1.9.21-release-633]
at kotlin.sequences.SequencesKt___SequencesKt.toList(_Sequences.kt:809) ~[kotlin-stdlib-1.9.21.jar:1.9.21-release-633]
at org.radarbase.output.path.PathFormatterPluginKt.toPathFormatterPlugins(PathFormatterPlugin.kt:14) ~[radar-output-restructure-2.3.3-SNAPSHOT.jar:unspecified]
at org.radarbase.output.path.FormattedPathFactory$Companion.toPathFormatter(FormattedPathFactory.kt:87) ~[radar-output-restructure-2.3.3-SNAPSHOT.jar:unspecified]
at org.radarbase.output.path.FormattedPathFactory$Companion.access$toPathFormatter(FormattedPathFactory.kt:80) ~[radar-output-restructure-2.3.3-SNAPSHOT.jar:unspecified]
at org.radarbase.output.path.FormattedPathFactory.addTopicConfiguration(FormattedPathFactory.kt:67) ~[radar-output-restructure-2.3.3-SNAPSHOT.jar:unspecified]
at org.radarbase.output.path.RecordPathFactory.init(RecordPathFactory.kt:69) ~[radar-output-restructure-2.3.3-SNAPSHOT.jar:unspecified]
at org.radarbase.output.path.FormattedPathFactory.init(FormattedPathFactory.kt:37) ~[radar-output-restructure-2.3.3-SNAPSHOT.jar:unspecified]
at org.radarbase.output.config.PathConfig.createFactory(PathConfig.kt:48) ~[radar-output-restructure-2.3.3-SNAPSHOT.jar:unspecified]
at org.radarbase.output.Application.<init>(Application.kt:67) ~[radar-output-restructure-2.3.3-SNAPSHOT.jar:unspecified]
at org.radarbase.output.Application$Companion.main(Application.kt:224) [radar-output-restructure-2.3.3-SNAPSHOT.jar:unspecified]
at org.radarbase.output.Application.main(Application.kt) [radar-output-restructure-2.3.3-SNAPSHOT.jar:unspecified]
This bug is became apparent during the security update process.
It seems that the mp-client configurations are not correctly passed from the root config (restructure.yaml) to the lower level configuration classes (FormattedPathFactory.kt in particular).