Description

Biotest table should have Chronologic age and age that user has at the biotest creation moment

Description

should have different stacks: Dev and Prod

Description

There should be a process to create a user in DB and cognito. This should send an email to user indicating the registration and request enter the app and change the password.

Description

It is need to create all app resources with serverless just as all permissions need by lambdas

Description

when a user is created can be helpfull to use a transaction to handle any error and avoid problems.

Description

Should get all user biotest. For admin it will be other kind of search

Description

Should return a user_uuid in json body

Description

Maybe use AWS is not really a good idea. I'd like to have the chance to create a docker to deploy this as API service

Description

This service will be an implementation of Golang validator which will return a slice with all errors of the request

Description

It is necessary to hold error handling of aws golang sdk to keep error status on request

Proposed Solution

Follow this article about this subject

Handling error on registry new user

Description

Couche can registry a new client who is not in the program. This should create him into the database with the necessary data to be asked to end his registration with cognito

HeartHealths
WeightClasifications

Description

User will be able to request a comparision beetwen 1 or many biotest selecting from which to what

Description

This is to show a biotest in the front

Description

This must be in a separate function

Reference

Description

So is need to find the way to do it with GIthub Actions to CD

Description

Might be great use postgres instance created for testing purpose into github actions

Describe the bug

Testing on AWS I found that all functions called by lambda.Start must return an error. This should be change by changing error handling or adding error interface and a nil to quick fix

Description

This will be use Environment Variables credencial specifing to create session

Description

This will help to keep our sensitive data save. Find how to configure this with serverless

Description

Create a class to send a function and its name to be registered and get the same methods to be called:

• GetFilter
• Run

Las funciones tendrán la misma firma y se construiran desde el main para que sean inyectados al CreateLambdaHandlerWDependencies

Description
Due some problems presented on transaction implementation on repositories we need other ORM option

Proposed Solution

Replace GORM by REL. REL has a test API that might be useful for this purpose

Alternatives considered
If anything it may be possible to keep GORM and work on my own ORM that satisfy all necessities

Description
I think isolating functionality in a lambda will help to just invoke lambdas to make the job and not duplicate code everywhere

Description

I'm not sure if entities will autoload all structs need to show data. [Here's ORM info](https://go-rel.github.io/association/#auto-saving-and-loading-association

Description

For privacy and security matters would be great to use uuid or any other unique parameter for this db registries. WIth this we can avoid share an Auto Incremented ID.

Description

User search implements filters so biotest should do the same.

Description

Create a test action to run when a PR is created and when there is a push in main branch

Description

This must be a separate function.

Description

Should be a query to search a user by its name or email returning it name and birthday

Describe the bug

Testing on AWS I found I was not sending a pointer to search on DB. This code solve theis problem.

handlers/get_catalogs/app.go#12

var catalogs = map[string]interface{}{
	"biotype":                &[]entities.Biotype{},
	"bone_density":           &[]entities.BoneDensity{},
	"heart_healths":          &[]entities.HeartHealth{},
	"roles":                  &[]entities.Role{},
	"weight_classifications": &[]entities.WeightClasification{},
	"genders":                &[]entities.Gender{},
}

_handlers/get_catalogs/app.go#33

return catalogsRepository.FindAllCatalogItems(ctx, handler)

Description

It is need to create a function to find user by differents filters

Proposed Solution

1. Create a function per search
2. Create declared filters to be get from front

Describe the bug

After deploy on AWS I found some issues that need fix

Description

Currently user is search by id, but must be found by UUID for security concerns

Description

Cognito implementation is need to send user data to allow the signUp to the app

Description

The front end should know all data can use to create a biotest. Through this lambda function will return the catalog required.

This should know if user have access to that catalog.

Description

Using a method is not useful. Must be loaded when service is starting

Description
When registry a user that is not a coach or admin this data is unneccesary