Juan Antonio Osorio

As we aim to have Minder be more useful outside of the scope of minder-server, we need to start moving utilities and dependencies outside of our bloated `internal` package. Moving...

### Please describe the enhancement The GitHub provider should contain all the handler logic, without access to the Minder database. ### Solution Proposal - ### Describe alternatives you've considered _No...

Remove database access from GitHub webhook handler

1

### Please describe the enhancement - ### Solution Proposal - ### Describe alternatives you've considered _No response_ ### Additional context _No response_ ### Acceptance Criteria _No response_

WIP: Remove per-entity tables

2

# Summary Fixes #4315 ## Change Type ***Mark the type of change your PR introduces:*** - [ ] Bug fix (resolves an issue without affecting existing features) - [x] Feature...

### Describe the issue Our logs have sporadic uses of `projectID`, `project_id`, with a similar problem happening for entities and providers. We should decide on one and use that around...

This is not used, and it also allows us to get rid of the `GetProperty` database call.

This provides us with some hardening that makes sure callers cannot even attempt to get an entity from a project that doesn't belong to them. Related to https://github.com/stacklok/minder/issues/4417

This provides us with some hardening that makes sure callers cannot even attempt to get an entity from a project that doesn't belong to them.

With all the necessary information within the `entity_instances` table, we can now dispose of the per-entity tables and rely solely on the central one.

Recursively list statuses for profiles in the hierarchy

1

If you're on a top level node, you should be able to see the status of all profiles in the hierarchy.