[MAGNOLIA-7805] Cloud native configuration for Magnolia bundles Created: 18/May/20  Updated: 25/Jun/21  Resolved: 25/Jun/21

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

Type: New Feature Priority: Neutral
Reporter: Michael Duerig Assignee: Unassigned
Resolution: Obsolete Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split from MAGNOLIA-7781 Follow-up - Improve profile and magno... Closed
Relates
dependency
relation
supersession
Template:
Acceptance criteria:
Empty
Date of First Response:
Epic Link: System configuration restrictions and externalisation
Sprint: Cloud Service 4
Story Points: 5

 Description   

We should investigate and implement a way to inject Magnolia configurations in a cloud native way. E.g. through a AWS Systems Manager Parameter Store or similar mechanisms.

Points to consider:

  • core properties such as `magnolia.resources.dir`, `magnolia.repo.home` etc (some of these are duplicated and re-defined in vitals webapp, which should be aligned).
  • LDAP integration
  • log4j configuration: Define log4j config file once for all environments/instances, e.g. custom log level/override vs. for 6 setups
  • Repository configuration
  • Testability

 


Generated at Mon Feb 12 04:26:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.