New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open

IswaryaaS opened this issue Sep 13, 2024 · 0 comments

Assignees

Labels

CONFIGfile_to_be_changed

Milestone

OKM v2.1.3_spec

Collaborator

IswaryaaS commented Sep 13, 2024 •

edited

Loading

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

IswaryaaS added the CONFIGfile_to_be_changed label

IswaryaaS added this to the OKM v2.1.3_spec milestone

IswaryaaS assigned openBackhaul

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment