Create get vulnerability details API #2207
Conversation
gcp/appengine/frontend_handlers.py
Outdated
| @@ -237,102 +237,6 @@ def vulnerability_redirector(potential_vuln_id): | |||
| return None | |||
|
|
|||
|
|
|||
| def bug_to_response(bug, detailed=True): | |||
There was a problem hiding this comment.
Moving these functions to utils.py so they can be used by both of api_handlers and frontend_handlers.
gcp/appengine/api_handlers.py
Outdated
| @@ -0,0 +1,47 @@ | |||
| # Copyright 2021 Google LLC | |||
There was a problem hiding this comment.
Create a new app for API
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
ZhangChen199102
force-pushed
the
get-vulnerability-data-endpoint
branch
3 times, most recently
from
985d7d8
to
4c2aee4
Compare
ZhangChen199102
force-pushed
the
get-vulnerability-data-endpoint
branch
from
4c2aee4
to
3f12c8a
Compare
|
Unless I'm misunderstanding the goal, rather than putting API code in the frontend as well, I think we can just put a link to the GET API endpoint on the page, or add a new handler to redirect requests ending in .json to the API endpoint. |
That was my understanding of the easiest way forward based on #2152 (comment) |
ZhangChen199102
force-pushed
the
get-vulnerability-data-endpoint
branch
from
3f12c8a
to
7a4ff83
Compare
|
So this time I just added a JSON Data field, with a GET vulnerability details link on the vulnerability details page: 
|
Issue: #2152
This PR introduces a new GET vulnerability details API