-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Teach Azure Filesystem to authenticate using DefaultAzureCredential in the Python SDK #24212
Conversation
R: @Abacn |
Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control |
Thanks @creste. Left some comments below the issue page. For the tests, to fix Lint and Formatter error, one could do
or
For RAT error, adding apache license at the top of new files (see other source files in the project) |
@@ -0,0 +1,2 @@ | |||
#!/bin/bash |
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.
e.g. We still need Apache License header here. And better move the raw .pem files here and write them to local at test run time as part of this script.
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.
I deleted create_certificate.sh
and moved the cert creation code to azure_integration_test.sh
, then I deleted cert.pem
and key.pem
to avoid the license header issues.
Generating the certificate on every test run adds just a second or two to the total test time.
I hope that solution is acceptable, but happy to change it if not.
Thank you for the tip! I ran those commands and fixed all linting errors in the files I modified. One exception is The PythonLint Jenkins job is failing with linting errors outside of the code I modified:
I'm not sure how to proceed. |
The remaining linting error is
not relevant to the change. It was introduced in #24022 but somehow not detected by linter. Never mind. |
Line 342 in b952b41
adding |
Codecov Report
@@ Coverage Diff @@
## master #24212 +/- ##
==========================================
- Coverage 73.46% 73.44% -0.02%
==========================================
Files 714 716 +2
Lines 96497 96557 +60
==========================================
+ Hits 70889 70921 +32
- Misses 24286 24314 +28
Partials 1322 1322
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Run Python 3.7 PostCommit |
integration test passed:
|
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.
Looks pretty solid to me. The integration test follows the same pattern of hdfs integration test we currently have. CC: @pabloem who reviewed blobstorageio if having any inputs.
btw could add a piece of information in CHANGES.md: https://github.com/apache/beam/blob/master/CHANGES.md |
ah I see, CHANGES will go to upcoming 2.44.0 here: Line 63 in 0265634
|
Tests not working yet due to TLS issue with Azurite.
Deleted cert and key files because they can't have a license header. Moved cert generation to azure_integration_test.sh.
@Abacn - Oh, thanks! I fixed CHANGES.md and rebased onto the latest master. |
CC: @tvalentyn if any inputs from Python review |
Fixes #24210.
Partially implements #20511.
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username
).addresses #123
), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>
instead.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.