-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Provider moving/microsoft azure #46254
Provider moving/microsoft azure #46254
Conversation
Ah no ... sorry - it's not |
tests need to be fixed/ |
Yeah, working on the tests right now. Should be done in the next couple of days! |
Cool. If you need any help - let me know :) |
Compat tests finally passed 🤯 |
Woooooooo! |
I am looking at the strange:
I think the problem is with some |
Ah yeah. |
Yeah I am also checking that one Jarek |
Thanks! |
Let's see 🤞 :) |
898c02e
to
9ff9a0d
Compare
Ah.. I forgot we need to set |
9ff9a0d
to
996e71b
Compare
Seems even more things - with imports... |
Green! Merging :) |
* Update provider.yaml * renaming files * moving microsoft.azure provider files to new folder structure * moving microsoft.azure provider files to new folder structure * Fixing breeze unit test params * Static checks fixes * Remove ms azure ignore from pytest args * Add pattern match to leave out ms azure providers * Fix pytest args for test types * Removed dead code * Added pytest fixtures to conftest.py * Added powerbi pytest fixture to conftest.py * Fixes for failing tests * Fixes for failing tests * Moved conftest.py * Fix for failing compat and provider tests * Move conftest.py to providers/microsoft/azure/tests/ and associated imports changes * Path changes to read resource files correctly * Removed microsoft from providers/tests * fixup! Removed microsoft from providers/tests --------- Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Relates to #46045, moving
microsoft.azure
provider to new folder structure.^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.