-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Build Cryptography wheel for Windows #18981
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
283dfdd
to
19ad598
Compare
b6c9e79
to
4e6ef06
Compare
79c27fc
to
e528dcd
Compare
8c9286a
to
694016b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but left a nit and a question
Review from FlorentClarret is dismissed.
Related teams and files:
- agent-delivery
- .builders/images/windows-x86_64/Dockerfile
77d56db
to
d0993c5
Compare
Review from FlorentClarret is dismissed.
Related teams and files:
- agent-delivery
- .builders/images/helpers.ps1
- .builders/images/windows-x86_64/Dockerfile
- .builders/images/windows-x86_64/build_script.ps1
Review from dkirov-dd is dismissed.
Related teams and files:
- agent-integrations
- .builders/images/helpers.ps1
- .builders/images/windows-x86_64/Dockerfile
- .builders/images/windows-x86_64/build_script.ps1
I'm closing this for now, as there are problems with the approach that involves this build and therefore for now this is not desirable. |
What does this PR do?
Forces the build of cryptography for Windows, so that we get our own wheels with dynamic linking to openssl.
I've done some testing on a Windows VM and this would seem to help us solve the current issue in a similar way that we do for Linux.
Motivation
FIPS support.
BARX-668
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged