Skip to content
This repository has been archived by the owner on Jan 23, 2024. It is now read-only.

More fields in the deploy table #413

Open
fbtravi opened this issue Dec 9, 2022 · 3 comments
Open

More fields in the deploy table #413

fbtravi opened this issue Dec 9, 2022 · 3 comments
Labels
type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@fbtravi
Copy link
Contributor

fbtravi commented Dec 9, 2022

HI,

Specifically analyzing the 'deployments' table, we don't have a field where we can identify the team responsible for the delploy or the environment.

Obviously we got it with a 'select' combination, but wouldn't it be nice to have that in this table?

I ask this because I am implementing the Four Keys in my organization and a more refined look will be needed.

I looked only with the eyes of GitLab, I don't know if the other parsers also have something like this.

I tried to read the project, but I'm still a little far from understanding how to do this

@fbtravi
Copy link
Contributor Author

fbtravi commented Dec 23, 2022

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.

@fbtravi
Copy link
Contributor Author

fbtravi commented Jan 11, 2023

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

@averikitsch averikitsch added the type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. label Jan 12, 2023
@fbtravi
Copy link
Contributor Author

fbtravi commented Jan 27, 2023

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

2 participants