FrankYang0529 opened a new pull request, #73426:
URL: https://github.com/apache/airflow/pull/73426

   This PR covers three items, because the first one cannot land alone:
   
   - [Go SDK: Replace the bundlev1 registry with 
airflow.Bundle](https://github.com/orgs/apache/projects/499/views/7?pane=issue&itemId=248986954)
   - [Go SDK: Register Mixed Lang task handlers with 
airflow.TaskHandler](https://github.com/orgs/apache/projects/499/views/7?pane=issue&itemId=248986974)
   - [Go SDK: Remove BundleProvider and the bundlev1server 
package](https://github.com/orgs/apache/projects/499/views/7?pane=issue&itemId=248987013)
   
   Changes:
   - `airflow.Bundle()` returns a `*BundleRef` whose exported methods are 
`Register` and `Serve`. A call to `airflow.TaskHandler(dagId, taskId, fn)` 
checks `fn`. If the check fails, the call panics with the dag_id and task_id in 
the message.
   - The task map is an unexported field of `BundleRef`. `bundle/bundlev1` 
moves to `internal/bundlev1` and keeps `Task`, `Bundle` and `EnumerableBundle`.
   - `Serve` keeps both modes. Its flags live on its own `FlagSet`, so 
importing `airflow` adds no flags to a program. `Serve` still accepts flags 
that the bundle defined on `pflag.CommandLine`.
   - `airflow` now imports the runtime, so `pkg/binding` can no longer import 
`airflow`.
   - ADR 0001 linked to the deleted `bundlev1server/server.go`, which fails the 
lychee hook. This PR turns the two links into plain text.
   
   Test:
   - `go test -count=1 ./...`
    <!-- SPDX-License-Identifier: Apache-2.0
         https://www.apache.org/licenses/LICENSE-2.0 -->
   
   <!--
   Thank you for contributing!
   
   Please provide above a brief description of the changes made in this pull 
request.
   Write a good git commit message following this guide: 
https://chris.beams.io/posts/git-commit/
   
   Please make sure that your code changes are covered with tests.
   And in case of new features or big changes remember to adjust the 
documentation.
   
   For user-facing UI changes, please attach before/after screenshots (or a 
short
   screen recording) so reviewers can assess the visual impact.
   
   Feel free to ping (in general) for the review if you do not see reaction for 
a few days
   (72 Hours is the minimum reaction time you can expect from volunteers) - we 
sometimes miss notifications.
   
   In case of an existing issue, reference it using one of the following:
   
   * closes: #ISSUE
   * related: #ISSUE
   -->
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   <!--
   If generative AI tooling has been used in the process of authoring this PR, 
please
   change below checkbox to `[X]` followed by the name of the tool, uncomment 
the "Generated-by".
   -->
   
   - [X] Yes - Claude Code
   
   <!--
   Generated-by: [Tool Name] following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   -->
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#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](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
 You can add this file in a follow-up commit after the PR is created so you 
know the PR number.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to