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

Define and implement a basic "data" service for sinking project and run data into #63

Open
rtyler opened this issue Mar 3, 2021 · 0 comments
Open

Define and implement a basic "data" service for sinking project and run data into #63

rtyler opened this issue Mar 3, 2021 · 0 comments
Assignees
@rtyler
Milestone
Self-hosted

Comments

@rtyler
Copy link
Owner

rtyler commented Mar 3, 2021

The object store can store artifacts and full logs, but there is still a need for a "data" service which can centralize active projects, and their relations to pipeline runs.

Whatever this is will need to be backed by a relational data store of some form. I'm thinking I can do something simple with sqlx and sqlite at the moment, but will need to provide a means to get into PostgreSQL or others later.
@rtyler rtyler added this to the Self-hosted milestone Mar 3, 2021
@rtyler rtyler self-assigned this Mar 3, 2021
@rtyler rtyler mentioned this issue Mar 3, 2021
Open
rtyler added a commit that referenced this issue Mar 4, 2021
@rtyler
Add a stub relational data service while I explore GraphQL
60e0b82 
See #63
rtyler added a commit that referenced this issue Mar 4, 2021
@rtyler
Pull in the async-graphql dependency for reldata
f017ea4 
I'm hoping that I can map objects through with graphql relatively easily so I
don't have to go full REST API for this service

See #63
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rtyler rtyler

Labels
None yet
Projects
None yet
Milestone
Self-hosted
Development

No branches or pull requests
1 participant
@rtyler