[MGNLRESTCL-49] Conceptualize versatile definitions Created: 02/Apr/19  Updated: 24/Jan/20  Resolved: 24/Jan/20

Status: Closed
Project: REST Client
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: Mikaël Geljić Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
is superseded by MGNLRESTCL-41 Verify Configuration of REST Clients Closed
is superseded by MGNLRESTCL-65 Declare rest calls using definitions ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Declarative REST clients
Story Points: 13

 Description   

Offer versatile definitions taking e.g. host-names, supported operations map, system access credentials (optionally linking to an entry from password-manager), remote endpoint version

  • Validate against diverse APIs (based on path-param vs. query-param)
  • Operations should support RO collection-fetching (querying, paging) as well as single-item reads
  • Consider multiple strategies for open vs. defensive API "exposure"

See also:



 Comments   
Comment by Christopher Zimmermann [ 07/May/19 ]

I collected my research here:

https://wiki.magnolia-cms.com/display/TEASYINT/Rest+Client+Declaration+research

and here:

https://wiki.magnolia-cms.com/display/TEASYINT/APIs+to+test+and+develop+against 

Comment by Mikaël Geljić [ 24/Jan/20 ]

—inspired MGNLRESTCL-65 and follow-ups, closing.

Generated at Mon Feb 12 10:42:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.