string-profile could be defined for /v1/record-service-request - Githubissues

openBackhaul / ExecutionAndTraceLog

List of records of service requests

Apache License 2.0

1 stars 7 forks source link

string-profile could be defined for /v1/record-service-request #413

Open at00825957 opened 4 days ago

at00825957 commented 4 days ago

Similar to https://github.com/openBackhaul/AdministratorAdministration/issues/377, we have a case in EATL where,

Currently, operationServer uuid of /v1/record-service-request (eatl-2-1-2-op-s-is-004) is being hardcoded in code

to get the operation-name for CreateLinkForReceivingServiceRecords
in waiting-stage whether the /v1/update-operation-key has been received for operation-server instance of eatl-2-1-2-op-s-is-004 after CreateLinkForReceivingServiceRecords callback.

Hence, a string-profile could be introduced for the operation-name "/v1/record-service-request".

OAS : string-profile paths definitions shall be added to Oam Layer
profileInstances.yaml : StringProfile shall be added
profiles.yaml: String profile definition shall be added
config.json: StringProfile shall be added for this string-value

Similar issue: https://github.com/openBackhaul/ExecutionAndTraceLog/issues/409