Similar to openBackhaul/AdministratorAdministration#377, we have a case in ALT where,
Currently, /v1/redirect-topology-change-information, /v1/update-ltp, /v1/delete-ltp-and-dependents, /v1/update-fc, /v1/update-fc-port, /v1/delete-fc-port is being hardcoded in code while
- creating operation-client instance during /v1/regard-application,
- selecting the operation-client instances during callbacks
Hence, a string-profile could be introduced for the operation-name "/v1/redirect-topology-change-information, /v1/update-ltp, /v1/delete-ltp-and-dependents, /v1/update-fc, /v1/update-fc-port, /v1/delete-fc-port"
- OAS : string-profile paths definitions shall be added to Oam Layer
- OAS: CreateLinkForInquiringTopologyChangeInformation, CreateLinkForProvidingUpdatedLtpInformation, CreateLinkForProvidingDeletedLtpInformation, CreateLinkForProvidingUpdatedFcInformation, CreateLinkForProvidingUpdatedFcPortInformation, CreateLinkForProvidingDeletedFcPortInformation :: the description for operation-name shall be updated to point to the string-profile instance
- profileInstances.yaml : StringProfile shall be added to each op-c
- profiles.yaml: String profile definition shall be added
- config.json: StringProfile shall be added to each op-c
Similar to openBackhaul/AdministratorAdministration#377, we have a case in ALT where,
Currently, /v1/redirect-topology-change-information, /v1/update-ltp, /v1/delete-ltp-and-dependents, /v1/update-fc, /v1/update-fc-port, /v1/delete-fc-port is being hardcoded in code while
Hence, a string-profile could be introduced for the operation-name "/v1/redirect-topology-change-information, /v1/update-ltp, /v1/delete-ltp-and-dependents, /v1/update-fc, /v1/update-fc-port, /v1/delete-fc-port"