[TRNSPRTPCE-670] Consider service-resiliency when creating services Created: 10/Jun/22 Updated: 20/Sep/23 Resolved: 07/Jul/22 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Chlorine |
| Type: | Story | Priority: | High |
| Reporter: | Jiao Thierry | Assignee: | Jiao Thierry |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 2 days | ||
| Original Estimate: | 2 days | ||
| Epic Link: | Demo SROL |
| Description |
|
Currently, creating a service (through service-create RPC) that contains service-resiliency entry does not work correctly. Because at the end of the service creation, the service-resiliency entry is discarded and it cannot be found in the service details. An update should fix this issue so that in the end, the service-resiliency will be present in the details of any service. Acceptance criteria : the code does not bring regression, associated Junit tests are provided
|