Skip to content
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

Implement CSV export #123

Closed
SamuelHassine opened this issue Jul 7, 2019 · 2 comments
Closed

Implement CSV export #123

SamuelHassine opened this issue Jul 7, 2019 · 2 comments
Assignees
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR) technical improvement Technical refactor or improvement is needed
Milestone

Comments

@SamuelHassine
Copy link
Member

Problem to Solve

The CSV export is currently handled by the frontend after a GraphQL API query. As STIX 2 bundle, this must be done asynchronously through the export worker.

Current Workaround

Use the current export (which is not perfect).

Proposed Solution

Implement a correct CSV export with:

  • columns selection
  • send the export job to the worker
  • wait for results

Additional Information

None.

@SamuelHassine SamuelHassine added feature use for describing a new feature to develop technical improvement Technical refactor or improvement is needed labels Jul 7, 2019
@richard-julien
Copy link
Member

I think we need to introduce a proper storage for export.
We can use minio (or S3) to store the file and provide a download link.

@SamuelHassine
Copy link
Member Author

@richard-julien: this will be in the next release, because we need to implement the CSV export of "lists" (for instance, give me the list of all intrusion sets in a CSV).

@richard-julien richard-julien changed the title Refactor CSV export Implement CSV export Oct 24, 2019
@SamuelHassine SamuelHassine removed this from the Release 2.0.1 milestone Oct 25, 2019
@SamuelHassine SamuelHassine added this to the Release 2.1.3 milestone Jan 23, 2020
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 24, 2020
SamuelHassine pushed a commit that referenced this issue Jan 24, 2020
* [api/frontend] Enhance export everywhere
* [api/client] Handle export of indicators in a specific entity
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR) technical improvement Technical refactor or improvement is needed
Projects
None yet
Development

No branches or pull requests

2 participants