string-profile could be defined for /v1/update-operation-key - Githubissues

openBackhaul / OperationKeyManagement

Manages keys required for consuming services between applications

Apache License 2.0

3 stars 8 forks source link

string-profile could be defined for /v1/update-operation-key #373

Open IswaryaaS opened 1 month ago

IswaryaaS commented 1 month ago

Similar to https://github.com/openBackhaul/AdministratorAdministration/issues/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