fix(job-attachments): remove dependency on pywin32 for submission code #250
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.
What was the problem/requirement? (What/Why)
We recently added a symlink threat mitigation that used
pywin32
for the Windows mitigation (on Unix we useO_NOFOLLOW
inopen
). This caused an issue in our integrated submitters because of the way the submitter code is loaded into DCC Python environments (non-standard), which preventspywin32
from being loaded up. Result is that users get an import error for the pywin32 modules when they try to submit with job attachments.What was the solution? (How)
Remove the dependency on
pywin32
for submission code, which is only the symlink threat mitigation for now. Instead, we usectypes
and call the Win32 APIs directly.What is the impact of this change?
DCC submitters can submit jobs with job attachments again.
How was this change tested?
Was this change documented?
No
Is this a breaking change?
No
E2E test
I crafted a test script that imported the updated code in this PR and called the function directly. It has two modes:
False
)True
)Test results
Test script