-
Notifications
You must be signed in to change notification settings - Fork 20
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.
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
chore: enhance bpdm interface documentation #237
chore: enhance bpdm interface documentation #237
Conversation
@@ -230,7 +231,7 @@ The call itself is not a API triggered call but automated by the process worker. | |||
However the administrator of the platform has the chance to retrigger the process in the scenario of an failure. | |||
|
|||
```diff | |||
! POST /api/administration/registration/application/{applicationId}/trigger-bpn | |||
! GET /api/catena/sharing-state | |||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Phil91 in this section we need to add the additional endpoint details of the second called endpoint to retrieve the BPN ++ can you please explain shortly inside the interface contract why we call 2 endpoints? Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good. @jjeroch do you want to double check?
90045a6
to
149bb36
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
conflict resolved
Description
Adjusted BPDM interface contract documentation
Why
Changes in the interface implementation as well as correction of incorrect mentioned details
Issue
n/a
Checklist