[MGNLREST-115] All endpoints are versioned Created: 13/Sep/17 Updated: 02/Nov/17 Resolved: 30/Oct/17 |
|
| Status: | Closed |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | to-estimate | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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)
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | REST Queries | ||||||||
| Sprint: | Saigon 116, Saigon 117, Saigon 118, Saigon 119, Saigon 120 | ||||||||
| Description |
|
All of the new endpoints should be versioned. User stories:
Capabilities:
Scenario Next Magnolia realizes we should really rename one of our properties and we release v2 of our endpoint system. All of bobs app continue to work because v1 is still supported. Bob is cool so he also creates "bob/v3" which implements our v2 output. And finally one of the frontend apps also upgrades to "bob/v3" while the others contineu to use v2 and v1. After a deprecation grace period,(and probably looking at his REST analytics that noone uses v1 anymore) Bob finally removes his v1 endpoint. Nice examples of the kinds of things that can change over time: |
| Comments |
| Comment by Mikaël Geljić [ 30/Oct/17 ] |
|
all current endpoints are already versioned in path. |