Scope

• Modules included in SaaS

Goal

• Get a list of all modules that contains configuration in JCR in SaaS
• Link the modules to the existing domain teams
• Share the approach and sample how Nucleus does it (externalize to Microprofile/YAML)
  • Sample: Admincentral Servlet MAGNOLIA-8286
  • Not every config fits in one solution

Expected next steps

• Share the list with all modules and its domain teams that they are aware which modules are still in JCR and would be required in order to bring our SaaS to a better 
• JCR config is a "stopper" for seamless updates
  • Approach 1: replace all SaaS-relevant JCR config at once (per domain decision)
  • Approach 2: replace as we need: whenever config need to be changed, is migrated before
  • Short-term: No more new config or updating config in JCR, not building anything new in JCR
  • Long-term: No more config available in JCR