Update celery provider conf imports to use common compat SDK

[aaron-y-chen]

related: #60000

There are two files I did not migrate.

1. celery/cli/definition.py
   It not allow to import from other path by below:
   

   airflow/scripts/ci/prek/check_cli_definition_imports.py

   Lines 41 to 45 in 821a4ad

   	# Allowed modules that can be imported in CLI definition files
   	ALLOWED_MODULES = {
   	"airflow.configuration",
   	"airflow.cli.cli_config",
   	}

   
   I think it should keep CLI startup lightweight, so I rolled it back.

2. celery/cli/celery_command.py‎
   It seems the new config has no celery.pool option, so the unit test fails.
   

   airflow/providers/celery/src/airflow/providers/celery/cli/celery_command.py

   Lines 293 to 295 in 4f2493d

   	if config.has_option("celery", "pool"):
   	pool = config.get("celery", "pool")
   	options.extend(["--pool", pool])

   
   Not sure if this is a bug.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

Generated-by: [Claude Opus] following the guidelines

---

• 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, 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.

[jason810496]

Nice!

[jason810496]

Sorry that I merged the PR too hastily. #64138 should fix this issue. Could you please help follow up on the remaining two CLI related files when you have time?

Thanks!

[aaron-y-chen]

Sure, I’ll do that tomorrow I wake up 😄

…

On Mon, Mar 23, 2026 at 11:51 PM Jason(Zhe-You) Liu < ***@***.***> wrote: *jason810496* left a comment (apache/airflow#64134) <#64134 (comment)> Sorry that I merged the PR too hastily. #64138 <#64138> should fix this issue. Could you please help follow up on the remaining two CLI related files after #64138 <#64138> is merged, when you have time? Thanks! — Reply to this email directly, view it on GitHub <#64134?email_source=notifications&email_token=ACW42LRASRMSPS6L6UDR2ND4SIWANA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJRGU4DINRTGMY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4115846331>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACW42LWKDYUMSRY3QPH6S3D4SIWANAVCNFSM6AAAAACW45U7J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMJVHA2DMMZTGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[aaron-y-chen]

Hi @jason810496, I opened an issue (#64201) for the celery_command.py bug. I'll handle the remaining two CLI related files after I solve this issue.