-
Story
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
- so that all instance configuration can reside in microprofile-config.properties or yaml
- so that instance configuration can leverage MicroProfile Config flexibility more broadly, including for existing code usages of MagnoliaConfigurationProperties, thus supporting a gradual upgrade to MP Config.
- consider equivalent MP Config profiles activation for author vs. public instances at least (maybe the other supported placeholders too).
Acceptance criteria