-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Yandex dataproc deduce default service account #35059
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
Yandex dataproc deduce default service account #35059
Conversation
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.
Maybe better make it as a part of Provider Configuration?
9d393da to
1d44ec6
Compare
|
Static checks are failing |
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.
| conf.get("yandex", "sdk_user_agent_prefix"), | |
| conf.get("yandex", "sdk_user_agent_prefix", fallback=""), |
Sorry, forgot to mark this PR as WIP. |
BTW, you or some one from the Yandex also could add link to Yandex Managed Service for Apache Airflow into Airflow Ecosystem, this placed into another repo, however changes could be done by simple click on The only one thing that I found that International Link to Yandex's managed service https://cloud.yandex.com/en/services/managed-airflow right now return 404 |
You could run this breeze release-management prepare-provider-packages yandex --version-suffix-for-pypi dev0 --package-format bothThis would create two distribution (wheel, source) in Good version of Docker: 24.0.6.
Good version of docker-compose: 2.22.0
...
Prepared provider package yandex in format both
===================================================================================
Summary of prepared packages:
Prepared:
yandex
===================================================================================
apache-airflow-providers-yandex-3.5.0.dev0.tar.gz
apache_airflow_providers_yandex-3.5.0.dev0-py3-none-any.whl
===================================================================================
All good! Airflow packages are prepared in dist folder
|
… use it in DataprocCreateClusterOperator
1d44ec6 to
c1e8f4f
Compare
c1e8f4f to
a716ec5
Compare
|
Thanks! Managed to build provider locally and test it on our managed solution. Works as expected |
31ebfbc to
3dd271c
Compare
|
Need to add test for this changes. For validate configuration, you might use airflow/tests/always/test_secrets_local_filesystem.py Lines 431 to 446 in eb450b9
airflow/tests/jobs/test_base_job.py Lines 113 to 123 in 1aa91a4
|
3dd271c to
2eddb69
Compare
|
Andrey, thanks for your approval! Is there anything else that should be done prior to merge this PR? |
|
Nope. It looks cool. |
|
Good to see this "per-provider" configuration feature... But that reminds me that we need a bit more "discovery" Look at "docs/apache-airflow-providers-celery" - there is configurtions-ref.rst which you have to add to yandex and you will have to also add configuration to index.rst @Piatachock also you should add link to https://github.com/apache/airflow/blob/main/docs/apache-airflow/configurations-ref.rst That reminds me that we should add pre-commit and automation - this all should happen semi-automatically or at least should be verified by pre-commit (but it does not yet). |
The change apache#35059 missed configuration docs but it did not fail the test suite. We need to improve it in the future, but for now just adding missing configuration documentations should fix doc build failures.
The change #35059 missed configuration docs but it did not fail the test suite. We need to improve it in the future, but for now just adding missing configuration documentations should fix doc build failures.
--------- Co-authored-by: Petr Reznikov <prez@yandex-team.ru>
The change apache#35059 missed configuration docs but it did not fail the test suite. We need to improve it in the future, but for now just adding missing configuration documentations should fix doc build failures.
New features for YandexCloud Provider: