Skip to content

[Part 2] Migrate connection UI metadata to YAML for more providers#62109

Draft
amoghrajesh wants to merge 2 commits intoapache:mainfrom
astronomer:migrate-to-yaml-phase-2
Draft

[Part 2] Migrate connection UI metadata to YAML for more providers#62109
amoghrajesh wants to merge 2 commits intoapache:mainfrom
astronomer:migrate-to-yaml-phase-2

Conversation

@amoghrajesh
Copy link
Contributor


Was generative AI tooling used to co-author this PR?
  • Yes - cursor with claude models

Migrate task execution, DAG processing, and logging providers: git, ssh, sftp, docker, cncf/kubernetes, standard, grpc,
opensearch, datadog, influxdb

Chose providers used for:

  • Remote task execution (ssh, sftp, docker, kubernetes)
  • DAG/code retrieval (git)
  • Standard filesystem and package operations (standard)
  • Service communication (grpc)
  • Remote logging backends (opensearch, datadog, influxdb)

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments