kristofferchr / personregistry Goto Github PK

We should use plantUML to document the system. We should have a plantuml diagram of the following:

• CI/CD pipeline
• Communication from user to AWS ECS cluster
• API and data model

Screenshots of the UI for usage in showcases:

1. Default ui
2. Messages when list is stored

Should investigate whether it is feasible to deploy to AWS ECS using github action.

We probably need to push image to AWS ECR and call CodeDeploy from workflow

The validation of name is too strict. It should be allowed to provide a name as such: "Will weaton". The backend fails on the whitespace in the middle

DoD:

• Whitespace is allowed in name

The current UI for the frontend is always in "edit mode". It would look better and be better UX if by default the list was in "view mode" and each row is editable by the click of a button. Same goes for delete. Component data-table satisfies the needs mentioned.

We should keep reload and save buttons to preserve the current draft functionality.

Example from vuetify:
https://vuetifyjs.com/en/components/data-tables/basics/#crud-actions

In order to get frontend and backend running when not using docker, ie. yarn run dev we had to add @crossorigin annotation for PersonlistController

We need to figure out a better approach, possibly properties in spring boot

If you add a new person and submit, then does the same again one ends up with multiple registrations. The reason is not updating persons state after submitting

DoD:

• Frontend uses axios or equivalent library to call API
• Changes to person should persist between reloads of the site

DoD:

• Frontend vue app is in main
• Backend spring boot app is in main
• Both builds to a deployable image

We should make the first iteration of the frontend by using local state without backend.

DoD:

• Should list out predefined persons
• Should be able to edit both age and name
• Should be able to delete a person
• Should be able to add new person
• When reload and submit is clicked there should be a spinner icon to simulate backend calls(no api calls will be made)

We should showcase basic auth in backend and frontend. Ideally one would implement OAUTH2 or openid connect, but since we do not have a database now we should use basic auth as a first iteration.

DoD:

• Login screen ui
• Backend has a fixed user that can be used with basic Authorization header. The user will be configured at build time when github workflow is running, which means it needs to be configurable through spring boot properties

The backend can be made separately of the frontend.

DoD:

• Design API for persons that should be RESTful, should have endpoints for CRUD
• Each person should have a unique ID. We should assume that there can be persons with the same name in a possible future
• Persons should persist in memory
• Test for controller. Should not mock service