[MAGNOLIA-8366] Create a list of all the modules that has configuration still in JCR Created: 14/Feb/22  Updated: 10/May/22  Resolved: 07/Mar/22

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: David Lopez Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: VN-Analysis, nucleus
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-8286 As a developer, I can add a servlet v... Closed
relates to MAGNOLIA-8341 As a developer, I need a feature flag... Closed
Template:
Acceptance criteria:
[ ]* List of modules with JCR config and the related domain team
[ ]* Sample of JCR configuration replacement as a show case
[ ]* Sharing the list + sample with the other domain teams
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Externalize user sensitive configuration
Story Points: 5
Team: Nucleus

 Description   

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


 Comments   
Comment by Roman Kovařík [ 23/Feb/22 ]

Looks like there is https://jira.magnolia-cms.com/browse/CLOUD-13 partially covering this.

Comment by Christopher Zimmermann [ 28/Mar/22 ]

I just (2022-03-28)  looked through the Config app on a SaaS instance and here are all the modules that have some JCR configuration:

  • dam
    • config
  • rest-integration
    • config
  • rest-services
    • rest-endpoints
  • scheduler
    • config
    • messageViews
  • project-configuration-events
    • commands
  • rendering
    • renderers
  • templating
    • renderers
    • templates
  • resources
    • commands
    • templates
    • config
    • renderers
  • ui-framework
    • dialogs
    • commands
  • ui-mediaeditor
    • mediaEditors
  • magnolia-usage-metrics
    • commands
  • task-management
    • config
  • ui-admincentral
    • dialogs
    • commands
    • templates
    • config
      • appLauncherLayout
    • userMenu
  • messageViews
    • virtualUriMappings
  • imaging
    • config
  • pages-app
    • commands
  • security-app
    • fieldTypes
    • dialogs
    • apps
  • enterprise
    • license
    • commands
  • dam-s3
    • commands
  • publishing-core
Generated at Mon Feb 12 04:32:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.