[MAGNOLIA-7811] Remove deprecated configurations style based on server and app name Created: 25/May/20  Updated: 27/Oct/22

Status: Accepted
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: 6.3.0

Type: Task Priority: Neutral
Reporter: Michael Duerig Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: artt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-7821 DOC: Environment variable for profile... Closed
relation
is related to MAGNOLIA-7781 Follow-up - Improve profile and magno... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Technical debt
Team: Foundation

 Description   

MAGNOLIA-7781 introduced profile style configuration and deprecated the current way of configuration based on server name and app name. At some point we should make the profile style the default and remove the now deprecated configuration style.

At the same time we can also further improve the error message when a non existing profile is specified (MAGNOLIA-7810) and include the names of valid profiles.



 Comments   
Comment by Maxime Michel [ 08/Nov/21 ]

mgeljic OK if we do this with 6.3?

Comment by Mikaël Geljić [ 09/Nov/21 ]

Tentatively yes, would bind this to the MicroProfile Config initiative too: MAGNOLIA-8200.

As a consequence, magnolia.properties should gradually be deprecated. A MP ConfigSource should expose them for backwards compatibility. And/or a MagnoliaConfigurationProperties bridge implementation, powered by MP Config.

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