Issues 56 and 57: Support executing PAL.ps1 from different directory and allow PS session log retention #58
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reintroduced capabilities added originally in PR#12, but lost during the v2.8.1 release.
Added support for calculating relative paths to various threshold files based on the location of PAL.ps1 instead of the PowerShell session's current working directory. This allows for PAL to be executed from anywhere without issue, which is beneficial for larger automation.
Added support for NOT clearing the PowerShell session at the beginning of execution, so a bigger automation script doesn't lose everything prior to PAL starting.
Re-enabled the debug logging to the user's temp directory, but added a timestamp to the file name, so that each execution doesn't wipe out the previous log.
Resolves #56
Resolves #57