Closed vimish closed 8 years ago
@Microsoft/ostc-devs
:-1:
I used CodeFlow for this, it actually worked really nicely! That was a recent change (just yesterday) that I made to OSTC-Docs.
You do NOT have signoff here, I'd like to see another iteration please. Thanks.
@Microsoft/ostc-devs
Please review the next iteration of the fix. Major changes are: 1) Default temporary directory is set in PAL when run as provider is loaded. Same location is retrieved from PAL and used during ExecuteScript call. 2) Unit test has been modified to set tmpDir location to testrunner location.
Pbuild has been run on all the dev systems and it was clean.
:-1:
I'd like to see another iteration on this please. Be sure that you only have one commit message.
Thanks.
Are you planning on posting another iteration on this? My last comments (asking for another iteration) was over a week ago.
Thanks!
Please review the next iteration of the fix. Major changes are: 1) Logic to store tmp directory location has been moved from systeminfo to RunAsProvider. 2) More testcase has been added for tmpDir functionality of ExecuteScript Method.
Pbuild has been run on all the dev systems and it was clean.
With my suggested changes above, I sign off. If you have any questions on my suggestions, feel free to reach out.
Please run a PBUILD prior to checkin to make sure everything works as expected ...
Merged #31
This is the SCXCore part of DCR to make monitoring script stored and executed from a custom location rather than hardcoded /tmp.
As part of the change a link /etc/opt/microsoft/scx/conf/tmpdir will be created during scx installation. It will point to /tmp by default. System admin can change this to point to any other location on the system.
When RunAs provider's ExecuteScript is called it will read the location and store the script there.