Un-suspend apache-airflow-providers-apache-beam

[olegkachur-e]

Under which category would you file this issue?

Providers

Apache Airflow version

version 3

What happened and how to reproduce it?

The beam provider has been suspended a while ago, because of beam python sdk dependency for the grpcio constraint.

The constraint issue seems to be resolved and released in a version of beam python sdk v.2.72.0.

What you think should happen instead?

So provider can be brought back in a "regular" status, being released and maintained.

Operating System

No response

Deployment

None

Apache Airflow Provider(s)

apache-beam

Versions of Apache Airflow Providers

No response

Official Helm Chart version

Not Applicable

Kubernetes Version

No response

Helm Chart configuration

No response

Docker Image customizations

No response

Anything else?

I need community guidance on how to "un-suspend" the provider?

Is it as straightforward as just reverting the #61926?

I don't mind submitting a PR if needed.

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[olegkachur-e]

Link the mailing list thread: https://lists.apache.org/thread/cnc2hwhc2x482zf26phvx6rsjgkrgtg1

[olegkachur-e]

I took a look on: https://github.com/apache/airflow/blob/main/providers/SUSPENDING_AND_REMOVING_PROVIDERS.rst#suspending-releases-for-providers it suggests:

The suspension will be lifted when the dependencies of the provider are made compatible with the Apache Airflow and with other providers - by merging a PR that removes the suspension and succeeds.

So I'll try to revert the suspension PR.

[potiuk]

Happy to help!