Is your feature request related to a problem? Please describe.
Monkey365 currently writes output by default under the module directory using the following format:
monkey365/monkey-reports/$GUID/$FORMAT/$FILE
The default output path should be changed so generated files are written outside the module directory. Additionally, the default folder name should also change from monkey-reports to monkey365-output.
The current behaviour is that when -OutDir is not specified, Monkey365 creates output inside the module. This behavior is documented here https://silverhack.github.io/monkey365/exporting/exporting-data/#data-location
Describe the solution you'd like
- When
-OutDir is specified, Monkey365 must keep using the provided path.
- When
-OutDir is not specified, Monkey365 must save data under the current working directory (./monkey365-output/$GUID/$FORMAT/$FILE)
The above must works on Windows PowerShell and PowerShell Core on Windows and Linux
Additional context
Monkey365 PowerShell module directory should contain the module files. Writing output there can cause problems when the module is installed in a protected or shared location, such as Program Files, a system-wide module path, a Docker image, or a CI/CD runner.
This change also helps reorganize the repository and module structure by keeping generated files outside the module path.
Related issues:
Is your feature request related to a problem? Please describe.
Monkey365 currently writes output by default under the module directory using the following format:
monkey365/monkey-reports/$GUID/$FORMAT/$FILEThe default output path should be changed so generated files are written outside the module directory. Additionally, the default folder name should also change from
monkey-reportsto monkey365-output.The current behaviour is that when
-OutDiris not specified, Monkey365 creates output inside the module. This behavior is documented here https://silverhack.github.io/monkey365/exporting/exporting-data/#data-locationDescribe the solution you'd like
-OutDiris specified, Monkey365 must keep using the provided path.-OutDiris not specified, Monkey365 must save data under the current working directory (./monkey365-output/$GUID/$FORMAT/$FILE)The above must works on Windows PowerShell and PowerShell Core on Windows and Linux
Additional context
Monkey365 PowerShell module directory should contain the module files. Writing output there can cause problems when the module is installed in a protected or shared location, such as Program Files, a system-wide module path, a Docker image, or a CI/CD runner.
This change also helps reorganize the repository and module structure by keeping generated files outside the module path.
Related issues: