[MGNLRESTCL-59] Separate RestClientRegistry functions, all operation related to RestClient should be done in another provider Created: 15/Jul/19 Updated: 15/Aug/19 Resolved: 08/Aug/19 |
|
| Status: | Closed |
| Project: | REST Client |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.0 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Dai Ha | Assignee: | Andrei Ichimescu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 1h | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Epic Link: | Declarative REST clients |
| Sprint: | Declarative REST 2, Declarative REST 3 |
| Story Points: | 3 |
| Description |
|
Currently, RestClientRegistry is handling RestClientDefinition registration and initializing/providing RestClient. This ticket aims to:
|