Skip to content

Increase finding.uid max lenght > 300 characters #7535

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jfagoagas opened this issue Apr 15, 2025 · 0 comments
Open

Increase finding.uid max lenght > 300 characters #7535

jfagoagas opened this issue Apr 15, 2025 · 0 comments
Labels
bug component/api severity/high Bug capable of collapsing large parts of the execution.

Comments

@jfagoagas
Copy link
Member

jfagoagas commented Apr 15, 2025

Steps to Reproduce

As discussed in this Prowler Community Slack 🧵 https://prowler-workspace.slack.com/archives/C045DAM2NE9/p1740529388847369

Tried to fix it in #7048 and #7498 but got issues with migrations since it requires to adquire an exclusive lock for the findings table. We need to try a different approach.

Expected behavior

We need to change the finding.uid field type from varchar to text and remove the 300 chars limit or increase the varchar size to more than 300 chars.

Actual Result with Screenshots or Logs

N/A

How did you install Prowler?

Cloning the repository from github.com (git clone)

Environment Resource

N/A

OS used

N/A

Prowler version

5.0

Pip version

N/A

Context

No response

@jfagoagas jfagoagas added bug status/needs-triage Issue pending triage component/api severity/high Bug capable of collapsing large parts of the execution. and removed status/needs-triage Issue pending triage labels Apr 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug component/api severity/high Bug capable of collapsing large parts of the execution.
Projects
None yet
Development

No branches or pull requests

1 participant