More fields in the deploy table about fourkeys HOT 3 OPEN

Thinking about solutions to this problem, I believe that a good way out is to put the project_id in the deploys table, as well as in the other tables.

For that, we should implement in each "parser" that includes the project_id in the "events_raw" table, and then send it to the rest of the tables.

This would be a way to build a query using an FK to find project information.

We still don't have this table with the project's information, but I believe this is the first step in making Four Keys information filterable.

from fourkeys.

Hello, it's been a while since this issue was opened, I would like to know what you think about it?

from fourkeys.

Hi,

In my organization we are going to start this implementation in a few weeks, we would love to develop something that contributes to open source.

So if we can continue with the discussion and find the best way, that would be great, so that our implementation can contribute to the community and not just sit on our fork.

@averikitsch @rogerthatdev @davidstanke

from fourkeys.