Manuel Carmona Pérez

## Issue update First of all, we are going to investigate the theoretical number of agents that could appear in a socket response (in past issues, we studied the limits...

## Issue update Let's calculate `len(c)` and `len(m)`. After talking with the core team, we know that the possible values for m are in the following variables: ``` WM_UPGRADE_SUCCESS WM_UPGRADE_PARSING_ERROR...

This comment contains an example to double-check the operations done before. Note that this example cannot exist in a real use case. The worst case will contain 97 dictionaries like...

## Issue update #### `GET /sca/{agent_id}` default query `SELECT {0} FROM sca_policy sca INNER JOIN sca_scan_info si ON sca.id=si.policy_id ` This query cannot be improved. #### `GET /sca/{agent_id}/checks/{policy_id}` default query...

## Issue update We are considering a full refactor to the API endpoint. When using the `process_array`, we are getting all the data from the databases (the default query is...

## Issue update I have completed the SCA framework (SDK and core) refactor. Apart from the way we are accessing the DBs, I have also updated the core functions to...

## Issue update After the last comment, I discovered that there were issues regarding the search and q parameters. Before the refactor, search and q were possible on values of...

We need to discuss the solution to this problem before trying to solve the `q` parameter issue. This issue will remain blocked until a new design/solution is proposed.

## Issue update After some design meetings, we have decided that this refactor could be achieved by following one of these two different workarounds: ``` Workaround 1: 1. Get a...

## Issue update I have developed a custom script that gets the SCA checks following the 2 workarounds mentioned in the last comment. During the script development, I found a...