[MGNLREST-116] Support multiple configured endpoint per workspace Created: 22/Sep/17  Updated: 31/Oct/17  Resolved: 29/Oct/17

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

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: to-estimate
Remaining Estimate: 0d
Time Spent: 5h
Original Estimate: 0.5d

Issue Links:
dependency
is depended upon by MGNLREST-115 All endpoints are versioned 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)
Date of First Response:
Epic Link: REST Queries
Sprint: Saigon 116, Saigon 117, Saigon 118, Saigon 119
Story Points: 5

 Description   

Currently only one registry-configured endpoint can be created per JCR workspace. The system should support multiple endpoints that use the same workspace as their data source.

For example I should be able to create one endpoint that lists all tours with all information, and another endpoint that lists all tours with only 3 fields, and still another endpoint that returns a single tour. All three endpoints will specify "tours" as the jcr workspace.



 Comments   
Comment by Christopher Zimmermann [ 11/Oct/17 ]

There was some discussion recently about custom endpoints no-longer being "under" the "/delivery/" url path and therefore needing a different configuration to handle OOTB security.

What if all configured endpoints were accessible via a url that followed "/delivery/" such as "/delivery/myFunnyEndpoint"?
curl -u superuser:superuser "http://<yourDomain>/.rest/delivery/myFunnyEndpoint/v1/about"
This would also make it clear that it is a "delivery" type of endpoint.

Comment by Dai Ha [ 30/Oct/17 ]

verify with magnolia-enterprise-pro-demo-bundle-5.6-20171029.233322-189-tomcat-bundle.zip, all endpoint & endpoint prefix configurations work.

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