[MGNLRESTCL-41] Verify Configuration of REST Clients Created: 14/Feb/19 Updated: 28/Oct/19 Resolved: 28/Oct/19 |
|
| Status: | Closed |
| Project: | REST Client |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Christopher Zimmermann |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| 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: | Easy Outbound REST | ||||||||||||||||
| Sprint: | Declarative REST 3, Declarative REST 7 | ||||||||||||||||
| Story Points: | 5 | ||||||||||||||||
| Description |
Currently Java is required to provision REST Clients. It should be possible with configuration and light development as well. Example:
Concrete examples:
Acceptance Criteria:
Notes A benefit is that a developer can configure the core details about a connection in one place, and then easily use that connection throughout the system. In contrast, if developers configure connections in multiple places, its more likely that one will not be updated correctly, and its hard to get an overview of all of the external systems used. This becomes even more important when the endpoints require mapping configurations and authentication credentials: passwords, secrets, tokens, and the like. |
| Comments |
| Comment by Christopher Zimmermann [ 28/Oct/19 ] |
|
Closing as done. Acceptance criteria are met. |