Web-Ui file upload structure

[lorriborri]

Situation

Currently, the normal file upload (e.g. my_custom.zip) only works for codeScan, which is outdated. Refer to the following environment variables:

PDS_JOB_SOURCECODE_UNZIPPED_FOLDER (outdated)
PDS_JOB_EXTRACTED_SOURCES_FOLDER (new structure)

For the new structure the PDS requires a structure for the zip files as follows: __data__/<unique reference name>/sourcecode. The corresponding configuration must reference the unique name.

Wanted

We do not want the user to pack his file manually in the required data structure. The user should just select a zip file.

Solution

We will implement the "old" way for all scan types with the following steps:

• using a fixed referenceID in the config.json that is build by the web-client ('__root__')
• when the archive is unzipped, the Filter must be adjusted to accept the fixed ref-ID as the root folder (No __root__ under __data__!)

[LefterisXefteris]

Hello there, i can contribute to this and other relavant issues.

[lorriborri]

Hi @LefterisXefteris

Thank you for your interest in contributing to our project! We appreciate your enthusiasm. The issue you picked might be a bit challenging for a first-time contribution, and it also requires some re-refinement. However, we have some other issues that would be great for getting started.

Please take a look at the issues labeled "good first issue" to find something more suitable. We are actively working on expanding this list to provide more beginner-friendly tasks.

Good first issues

These should provide a good introduction to our codebase and processes. If you have any questions or need further assistance, feel free to ask. You can also find contribution guidelines in our CONTRIBUTING.md.

Best regards,
Laura