-
Notifications
You must be signed in to change notification settings - Fork 16
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
add a csv/google sheets front end to the cre rest api #25
Comments
I'd be happy to take this on. Could you provide a bit more information about the scope of this, please? |
thanks for the interest! this is awesome! updated the original ticket description |
I started looking into the export functionality just now! 🎉 Spreadsheet Export from REST APIShould this be a standalone tool under this repo, or should it rather extend the existing app under OWASP/common-requirement-enumeration with an additional button? I think from a UX perspective something like this could be nice: Clicking on the Is this what you imagine? Thanks! |
it should handle CRE, pages standard pages and generic search pages.
the button on the page is exactly what i had in mind!
…On Mon, 13 Dec 2021 at 20:31, Flo ***@***.***> wrote:
I started looking into the export functionality just now! 🎉
Few more questions:
Spreadsheet Export from REST API
Should this be a standalone tool under this repo, or should it rather
extend the existing app under OWASP/common-requirement-enumeration
<https://github.com/OWASP/common-requirement-enumeration> with an
additional button? I think from a UX perspective something like this could
be nice:
[image: image]
<https://user-images.githubusercontent.com/6052785/145883219-498b82ee-b0fd-412e-a007-0182edfa3104.png>
Clicking on the Export button would then trigger the creation of a
spreadsheet from the current API call, in the above case, a spreadsheet
containing the top10 from 2017.
Is this what you imagine?
Should it also handle individual standard pages, eg
https://www.opencre.org/standard/Top10%202017/section/A2_Broken_Authenticationn
?
Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#25 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMCRHX455NAVRITYSOF7TDUQZJ2FANCNFSM4SAZHCFQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
There's currently no way to import/export data to/from the REST API.
This ticket has two parts:
Given a REST call, add the ability to export the results into a google sheets spreadsheet which allows humans to get the mappings into a CSV format. This is already partly implemented (utils/spreadsheet_utils.py) but we haven't implemented any API plumbing for it.
There's a way for Authorissed users to submit a spreadsheet that follows the template and import mappings from it.
This involves some openidconnect integration and some way of allowing which users can submit mappings + plumbing for the parsers to receive a spreadsheet url. This functionality already exists via the cmd api but haven't managed to plumb the openid connect stuff.
The text was updated successfully, but these errors were encountered: