[MGNLREST-304] Support configuration environments in delivery endpoints Created: 04/May/21  Updated: 08/Jul/21  Resolved: 30/Jun/21

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

Type: New Feature Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Andrei Ichimescu
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-8116 Support configuration environments in... Closed
duplicate
supersession
Template:
Acceptance criteria:
Empty
Epic Link: SaaS project configuration
Sprint: Cloud Service 10, Cloud Service 11, Cloud Service 12
Story Points: 21

 Description   

TIMEBOX

[DONE] Use the 5-story point equivalent effort time to estimate whether the points below are achievable, extract the follow-up issues if needed
[IMPLEMENTATION] estimates much higher and was done in the scope of this ticket.

Base AC

  • make sure that delivery endpoints dynamically alter their behaviour based on the state of the configuration env selected (implementation-wise)
  • how does one communicate a desired configuration env from e.g. an http client request (e.g. i want to test my endpoint against several configurations, how do i communicate which config env to use with a request - over a request header? query param? cookie? ..)

Generated at Mon Feb 12 06:58:36 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.