[PUBLISHING-100] Externalise publishing configuration Created: 02/Mar/21  Updated: 24/Jan/24  Resolved: 05/Mar/21

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: None
Fix Version/s: 1.4.0

Type: Task Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Rabie Hayoun
Resolution: Fixed Votes: 0
Labels: cloud
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
Problem/Incident
causes PUBLISHING-318 Remove default receiver config from m... In Progress
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: System configuration restrictions and externalisation
Story Points: 8
Team: Nucleus

 Description   

Config to externalise:

  • Receiver URLs and active state
  • Logging
  • Publication strategy (uuid vs path)

Define relevant personas, consider this configuration private (Mgnl admin only, not exposed to project developers) (??)

TODO:

  • move the issue to Publishing module
  • consider chipping out a ticket of the Helm

DEV notes:

  • Migrate to MicroProfile configuration
  • update infra configuration accordingly

Generated at Mon Feb 12 10:35:24 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.