This repository has been archived by the owner on Feb 1, 2023. It is now read-only.
Add Basic CRUD backend using DynamoDB #17
Assignees
Labels
enhancement
New feature or request
Comments
Closed
d47853
added a commit
that referenced
this issue
Jun 12, 2020
d47853
added a commit
that referenced
this issue
Jun 19, 2020
d47853
added a commit
that referenced
this issue
Jun 19, 2020
d47853
added a commit
that referenced
this issue
Jun 22, 2020
Merged
d47853
added a commit
that referenced
this issue
Jun 24, 2020
* gh-17 Updated dependencies and Added Graph Storage backend * Added Delete lambdas. Need to integrate with existing code * gh-17 integrated delete handler * Integrated get graphs into REST API * gh-17 Building * gh-17 Fixed Lambda functions * gh-17 Fixed Linting * gh-17 corrected existing tests * gh-17 halfway through testing * gh-17 halfway through testing * gh-17 finished testing * gh-17 Added API documentation * gh-17 added config docs * gh-17 Fixed linting errors * gh-17 preparing for PR * Update README.md Co-authored-by: t11947 <53758970+t11947@users.noreply.github.com>
macenturalxl1
added a commit
to macenturalxl1/Kai
that referenced
this issue
Jan 12, 2021
Gh 07 ui develop
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Create a DynamoDB table as part of the deployment.
Integrate the Table with the existing Lambda Functions
When a graph is added (initially by providing a graphId and schema) via the APIGateway, an entry should be created in the DynamoDB table containing it's id, the owner and a URL which should take the user to the Gaffer REST API. Until #15 or some other mechanism for deploying a Gaffer instance is done, we can stub this value.
When a graph is deleted, the row in the DynamoDB table should be deleted.
When the API is queried for all the graphs, all the graphs the user owns in the DynamoDB table should be returned.
The text was updated successfully, but these errors were encountered: