[MAGNOLIA-7809] Allow magnolia profile to be specified via system property Created: 25/May/20  Updated: 26/Jun/20  Resolved: 05/Jun/20

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

Type: Improvement Priority: Neutral
Reporter: Michael Duerig Assignee: Michael Duerig
Resolution: Fixed Votes: 0
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
documentation
to be documented by MAGNOLIA-7821 DOC: Environment variable for profile... Closed
Template:
Acceptance criteria:
Empty
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)
Documentation update required:
Yes
Epic Link: Product improvements for Cloud project features
Sprint: TE 3
Story Points: 2

 Description   

Since MAGNOLIA-7781 a configuration profile can be specified through the MAGNOLIA_PROFILE environment variable. We should extend this mechanism such that the profile could also be specified as a system property.

The corresponding pattern would then change from ${env/MAGNOLIA_PROFILE} to just ${MAGNOLIA_PROFILE}.

Implementation wise I suggest to inject that binding through the MagnoliaInitPaths mechanisms, which already provides bindings for server name etx.


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