Skip to content
This repository has been archived by the owner on May 7, 2021. It is now read-only.

[BE] Build out the OneApp GraphQL server foundation #11

Closed
17 tasks done
ronaldheft-gov opened this issue Aug 5, 2020 · 5 comments
Closed
17 tasks done

[BE] Build out the OneApp GraphQL server foundation #11

ronaldheft-gov opened this issue Aug 5, 2020 · 5 comments
Assignees

Comments

@ronaldheft-gov
Copy link
Contributor

ronaldheft-gov commented Aug 5, 2020

Develop the foundation for a solid GraphQL server that can be the foundations for the new OneApp redesign.

Development process / builds

  • Basic server build process: linting, live reloads, etc
  • Package application into a single executable that could be run on existing OneApp servers
  • Logging framework
  • Mock server for UI development
  • Import the OneApp development database into a reusable Docker container that all developers can utilize
  • Import the OneApp development database correctly
    • The database currently has packages that are not compiling due to issues with the export from the existing database
    • This can be resolved by re-exporting and manually fixing the import errors
  • Introduce a unit testing framework for GraphQL
  • Setup different environment configurations
  • Move over to NJ repo
  • Setup dependabot

Application

  • Configure a GraphQL server
  • Build a solid modularized structure for working on GraphQL endpoints
  • Prototype connecting GraphQL to the Oracle database
  • Prototype using Oracle stored procedures against the real OneApp development database (Blocked until database is imported correctly. Verified process for stored procedures works, just not against the real data until import is fixed.)
  • Authentication for the API
    • User credentials / API key to access the API, i.e. you have to have API credentials to create applications, etc. and random internet traffic won't be accessing data from the API without credentials
  • Access controls for the API
    • Ensuring only the data created by the user is accessible, i.e. users can't access other users data
  • Field-level validation for the API
    • Data sent to the API conforms to standards, i.e. email addresses are in email format, etc.
@ronaldheft-gov ronaldheft-gov self-assigned this Aug 5, 2020
@ronaldheft-gov ronaldheft-gov added this to the Build 1 milestone Aug 5, 2020
@ronaldheft-gov ronaldheft-gov added this to Doing (Development) in NJ OneApp (v.1.0) Aug 5, 2020
@ronaldheft-gov
Copy link
Contributor Author

Field-level validation done.

@ronaldheft-gov
Copy link
Contributor Author

Have basic JWTs working right now

@ronaldheft-gov ronaldheft-gov moved this from Doing (Development) to Development Done in NJ OneApp (v.1.0) Aug 17, 2020
@Samara-Strauss Samara-Strauss removed this from the Build 1 milestone Aug 18, 2020
@Samara-Strauss
Copy link

@ronaldheft-usds is this ticket done? I see all the items in the checklist have been completed. Let me know if there is anything else you need to do, or if you need Mike to look at anything.

If it's done, can you do the following:

  • Add an estimate. We are using the scale 1-small, 2-medium, 3-large to rate our tickets. I would say 1 = quick, 2 = a couple days, 3 = a week of work.
  • Once you add an estimate, close out the ticket.

@Samara-Strauss Samara-Strauss changed the title Build out the OneApp GraphQL server foundation [BE] Build out the OneApp GraphQL server foundation Aug 18, 2020
@Samara-Strauss
Copy link

Samara-Strauss commented Aug 31, 2020

Can I close this ticket?

@ronaldheft-gov
Copy link
Contributor Author

All good to close!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
NJ OneApp (v.1.0)
Development Done
Development

No branches or pull requests

2 participants