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.

Sign up for GitHub

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

Jump to bottom

Extend forceDelete option to all GraphQL deletion related functions #6969

Open
JeremyCloarec opened this issue May 14, 2024 · 1 comment
Open

Extend forceDelete option to all GraphQL deletion related functions #6969

JeremyCloarec opened this issue May 14, 2024 · 1 comment
Labels
feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team

Comments

@JeremyCloarec
Copy link
Contributor

To speed up development, we used the forceDelete option within certain methods (stixDelete in stix.js).
But there is no way to force the deletion of entities to be permanent on the graphQL side.
We could add a forceDelete parameter to all deletion related functions in graphQL. That way, it is the one calling the graphQL method that will be responsible for deciding wether to permanently delete the entity or not.

See #6940 for more context
@JeremyCloarec JeremyCloarec added feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team labels May 14, 2024
@JeremyCloarec JeremyCloarec mentioned this issue May 14, 2024
Merged
5 tasks
@labo-flg
Copy link
Member

This means improving our graphQL API so that users can decide or not to put elements in the trash or permanently delete them, in their scripts for instance.

Improving the gql API could also mean doing the same with the client-python, to expose this option too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@labo-flg @JeremyCloarec