Microsoft
Microsofttimurengin
Hello kind sir,
Adding additional tasks (more then 1) in the yml file where you specifiy workingDirectory causes DevOps pipeline to overwrite each tasks tracking_table_<id>.csv. This is with the default powershellscript created by connecting Sentinel out the box.
Example issue:
Task 1 creates a tracking table entry, holds it in "memory".
Task 2 creates a tracking table entry, holds it in "memory".
When its time to write to the repo, the actual file tracking_table_<id>.csv it cleans out Task 1s jobb as Task 2 lands after.
This causes unwanted massive runtimes and redeployments if anything within the task1 workingDirectory. Task 1 in my case is the default repos with 200 analytic rules and configs while task 2 is custom deployments. I could revert the order to cut down on the runtime and let the largest workingDirectory be the last task in the pipe, but the issue would remain.
Any solutions from your end? (to the default ps1 script that is created).
As additional input:
I tried adding the functionality myself to the ps1 script, but im at best novice at both powershell and devops.
Greatly appreciated.
