[TRNSPRTPCE-699] Updating TAPI connectivity service list Created: 23/Oct/22 Updated: 20/Sep/23 |
|
| Status: | Open |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Jonas Mårtensson | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
When TAPI feature is enabled, an initial mapping of existing services to TAPI connectivity services is performed. But if additional services are created using the OpenROADM service API, these are not added to the TAPI connectivity service list. It would be nice if these were kept in sync, regardless of which API is used to create a service. |