The full port scans were not properly accounting for exclude files when ran directly from the CLI. This could potentially be detrimental if the tool is ran without first using the scoper operation.
🧪 Testing
Added scripting logic to account for optional exclude files
Loaded tool on a virtual machine and ran tool against test range
Used the following commands to ensure full port operation worked with and without exclude files:
MESA-Toolkit -o full -p <Project_Name> -i <Target_File>MESA-Toolkit -o full -p <Project_Name> -i <Target_File> -e <Exclude_File>
✅ Pre-approval checklist
[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
🗣 Description
This PR satisfies issue #5
💠Motivation and context
The full port scans were not properly accounting for exclude files when ran directly from the CLI. This could potentially be detrimental if the tool is ran without first using the scoper operation.
🧪 Testing
MESA-Toolkit -o full -p <Project_Name> -i <Target_File>
MESA-Toolkit -o full -p <Project_Name> -i <Target_File> -e <Exclude_File>
✅ Pre-approval checklist
✅ Pre-merge checklist