-
Notifications
You must be signed in to change notification settings - Fork 8
string-profile could be defined for /v1/update-operation-key #373
Copy link
Copy link
Open
Description
Similar to openBackhaul/AdministratorAdministration#377, we have a case in OKM where,
Currently, /v1/update-operation-key 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/update-operation-key".
- OAS : string-profile paths definitions shall be updated in Oam Layer
- OAS: CreateLinkForUpdatingOperationKeys :: 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
Reactions are currently unavailable