We had to enlarge this field in past, because it was to short for our needs.
There might be some use cases project_id should be larger than the currently allowed 40 characters.
Example
For Example mapping a Github repository name as a SecHub project_id or even contain the repository name and the Github organization. Github for example allows:
organization name: 39 characters
repository name: 100 characters
This means somehting like $ORGNAME_$REPONAME could be too large for the current 40 characters
Solution
Find a good length that is sufficient, like for example 150 characters because this project id is part of the report file name. Filenames have a limited length by the underlying OS. E.g. linux 255 characters.
Situation
We had to enlarge this field in past, because it was to short for our needs. There might be some use cases
project_idshould be larger than the currently allowed 40 characters.Example
For Example mapping a Github repository name as a SecHub
project_idor even contain the repository name and the Github organization. Github for example allows:This means somehting like
$ORGNAME_$REPONAMEcould be too large for the current 40 charactersSolution
150characters because this project id is part of the report file name. Filenames have a limited length by the underlying OS. E.g. linux 255 characters.project_idvarchar database field.