Add graphql mutations to delete builds and invocations #80
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When running in a production environment with lots of invocations, builds and targets, the database can bloat up pretty big pretty quickly, which has storage cost and performance implications. A mechanism is needed to manage the size of the database.
This PR adds a few graphql API endpoints to manage invocations and builds. It also updates the backend schema to include cascading delete relationships as appropriate.
New Methods:
This process does not currently support blob cleanup. I plan to add that in a future PR. Also in a future PR I plan to add an option to configure and run a process on a schedule to automate this task
Also updates golden files as appropriate