You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a renku-graph API user, I'd like the knowledge-graph exposes a Project Create API that performs all the necessary backend operation for a user.
The problem
Apparently, the project creation process is slightly complex and requires certain steps to happen in order. While it's possible to do all the work in the UI it's rather a backend task and what's probably more important would need to be replicated in all the renku clients.
Acceptance criteria:
The KG service to expose a new POST projects API
The API to take all the relevant properties in the payload (to be defined precisely by finding out the bare minimum needed by the Core API)
The API to expect a GL auth token can be used against the Core API
The API to enforce user authentication in GL
The API to block until all the operations are finished
The API to return 201 CREATED for successful creation
The API to return 400 BAD_REQUEST for invalid payload
The API to return 400 BAD_REQUEST in case the project already exists (additional call to GL needs to be done to check this)
The API to return 401 UNAUTHORIZED for auth failures
The API to return 500 INTERNAL_SERVER_ERROR for failures during creation
The API to pass eventual error messages coming from the external calls back to the caller
The API to call the GL Create Project API The project is created in GL by Core's templates.create_project API
The API to wait for the project to be available (GL's Project Details API to return 200 OK) The API to create the project in the TS - no explicit waiting/polling needed
The API to activate the project with the webhook service
The API to wait for the project to be available in the TS (KG's Project Details API to return 200 OK) No need for waiting for the activation by calling the Project Details API as the project is created in the TS by a direct call
The API to call the KG's Project Update API to adjust visibility, images and other properties that are not set during creation
Create OpenAPI docs and update the README
write graph renku acceptance tests
The text was updated successfully, but these errors were encountered:
As a renku-graph API user, I'd like the knowledge-graph exposes a Project Create API that performs all the necessary backend operation for a user.
The problem
Apparently, the project creation process is slightly complex and requires certain steps to happen in order. While it's possible to do all the work in the UI it's rather a backend task and what's probably more important would need to be replicated in all the renku clients.
Acceptance criteria:
POST projects
API201 CREATED
for successful creation400 BAD_REQUEST
for invalid payload400 BAD_REQUEST
in case the project already exists (additional call to GL needs to be done to check this)401 UNAUTHORIZED
for auth failures500 INTERNAL_SERVER_ERROR
for failures during creationThe API to call the GL Create Project APIThe project is created in GL by Core's templates.create_project APIThe API to wait for the project to be available (GL's Project Details API to returnThe API to create the project in the TS - no explicit waiting/polling needed200 OK
)The API to wait for the project to be available in the TS (KG's Project Details API to returnNo need for waiting for the activation by calling the Project Details API as the project is created in the TS by a direct call200 OK
)The API to call the KG's Project Update API to adjust visibility, images and other properties that are not set during creationgraphrenku acceptance testsThe text was updated successfully, but these errors were encountered: