Migrate yandex connection UI metadata to YAML - #63506
Merged
potiuk merged 1 commit intoMar 14, 2026
Merged
Conversation
fat-catTW
marked this pull request as ready for review
March 13, 2026 10:53
potiuk
approved these changes
Mar 14, 2026
abhijeets25012-tech
pushed a commit
to abhijeets25012-tech/airflow
that referenced
this pull request
Apr 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Updated providers/yandex/provider.yaml for connection type yandexcloud
Changes
Added ui-field-behaviour.hidden-fields to hide default connection fields (
host,schema,login,password,port,extra)Added conn-fields definitions for:
service_account_jsonservice_account_json_pathoautholder_idpublic_ssh_keyendpointRegenerated providers/yandex/src/airflow/providers/yandex/get_provider_info.py so the runtime provider info reflects the YAML changes.
related: #62345
Was generative AI tooling used to co-author this PR?
Generated-by: Copilot following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.