juanvf / personal_bot Goto Github PK

Dependencies:

• You can assume you have a service where you can use the following db repository data https://github.com/JuanVF/personal_bot/blob/main/repositories/currencies.go to consume the live value of the currencies. Using the feature that comes from: #2
• You can assume you will have a field to save the payments as unprocessed #5

Context:

An user or an external trigger must be able to request a new payment endpoint in order to generate its latest payments that comes from its personal email. The user can expect the data that comes from its personal email will be saved in the Payments Table in database.

What is expected to have:

• A new endpoint /payments/generate with POST method. This method must be protected using the Verify Token Middleware in the apigw/auth file. Also will receive the ID Token from Google OAuth, you can assume this ID Token is in JWT format and if you decode it and verify it, you can get the user email.

{
    "id_token" : "<Google ID Token>"
}

• A new payment service for this feature, where you at least: decode de ID Token and get the user email, get the user id using that email, get the last thread id readed by the bot, and read the latest emails from the user mail and then process then, so you get a [ ]*Payment type for each new payment, all of them marked as unprocessed.
• You will use the Open AI service to classify and get the tags for each service. Now this AI will return tags that might not be in DB, is up to you to decide whether to store this new tags and find a way to not repeat them, or change the tags structure. Also, the structure for the prompt is the follow:

payment: <the email data>\ntags:

Then GPT-3 will return the tags possibly, because is an AI, in the next format

tag1, tag2, ..., tagN\n

• The processed emails to be stored in the DB Payments Table.
• The endpoint will return an empty body with 200 OK Http Status.

Nice to have:

• As you can see the service does many request, so the endpoint will be slow. That is an expected behaviour and is OK since this endpoint will be executed once a day, but if you find other workaround to make it faster, that can be discussed.

Spikes for this issue:

• #1

Given the implementation flow proposed in the spike, the goal of this issue is to implement it to the project.

What is expected to have:

• A service where we can get the live value of the currencies given the name of the currency that comes from databse.

Context:

An user will have unprocessed payments to be updated in his general balance. An user or an external trigger must be able to request a new balance endpoint and have a current state of its balance.

What is expected to have:

• A new endpoint balances/update with POST method. This method must be protected using the Verify Token Middleware in the apigw/auth file. Also will receive the ID Token from Google OAuth, you can assume this ID Token is in JWT format and if you decode it and verify it, you can get the user email.

{
    "id_token" : "<Google ID Token>"
}

• A new balance service, where you query the unprocessed payments, and update the corresponding user balance in DB.
• You also must update the new payments to be marked as processed.

The project currently has two currencies to be supported, CRC and USD. We need to find a data source for getting the current value of the currencies.

What is expected to have:

• A website or API to get the live value of the CRC and USD currencies.
• A flow of how to implement it.
• A service where we can get the live value of the currencies given the name of the currency that comes from database.
• You must support the next DB Repository: https://github.com/JuanVF/personal_bot/blob/main/repositories/currencies.go

Nice to have:

• The core goal of the project is to support multiple payments data sources, so it means the user might have different Costa Rican Banks. So a nice to have might be having the different live currency values from the different Costa Rican Banks.

Context:

All the current payments are stored in DB, but there is no way to know if they were already processed. The idea is to add a new field to the payments table to be able to mark the payments as processed or unprocessed.

What is expected to have:

• A new field to mark the payment as processed or unprocessed, by default it should be marked as unprocessed.

Nice to have:

• Doing this might be slow, so, you are allowed to find other way to identify the unprocessed payments or doing it faster.