Docs: Add prominent deprecations notice via css

[geraj1010]

---

Updated deprecated Bigquery docstrings with the .. warning:: admonition and added custom CSS styling, which will apply to all .. warning:: admonitions found in docstrtings.

closes #41532

[ashb]

Could you include before and after pics please?

And if we use .. warning:: anywhere else before and after of one those too please

[kaxil]

Screenshots are here: #41532 (comment)

[geraj1010]

For BigQueryExecuteQueryOperator:

Before:

After:

There are other operators that use .. warning:: in their docstring, here is CloudDataTransferServiceCreateJobOperator

Before:

After:

So the styling appears to apply to all docstrings, which use the .. warning:: admonition (since the CSS is in docs/sphinx_design/static/custom.css) . If that is an issue, I could create a .css specifically for Google Providers if that helps. Then that would restrict the styling to Google Providers.

[geraj1010]

@ashb Did I provide enough screenshots? Are there any other concerns?

[kaxil]

We should do the same for all deprecated operators too

[geraj1010]

We should do the same for all deprecated operators too

That would be great. I could go through and apply this update to all deprecated operators. Unfortunately, it's a manual effort. I did mention something about extending the Sphinx AutoAPI extension (#41532 (comment)), but that would take more work for sure.

[potiuk]

You need to rebase/resolve conflicts @geraj1010

[omkar-foss]

I could go through and apply this update to all deprecated operators. Unfortunately, it's a manual effort. I did mention something about extending the Sphinx AutoAPI extension (#41532 (comment)), but that would take more work for sure.

No problem, I can help with applying this update to all deprecated operators.

@kaxil @potiuk Shall I raise a separate PR with commits from this PR or something else, please let me know. Thank you :)

[potiuk]

@kaxil @potiuk Shall I raise a separate PR with commits from this PR or something else, please let me know. Thank you :)

If @geraj1010 is ok with it, absolutely - feel free.

[kaxil]

I could go through and apply this update to all deprecated operators. Unfortunately, it's a manual effort. I did mention something about extending the Sphinx AutoAPI extension (#41532 (comment)), but that would take more work for sure.

No problem, I can help with applying this update to all deprecated operators.

@kaxil @potiuk Shall I raise a separate PR with commits from this PR or something else, please let me know. Thank you :)

I think we can merge this one to credit @geraj1010

[kaxil]

I resolved the conflict, and merged

[kaxil]

Verified it locally:

[kaxil]

@eladkal Worth including this change in the next batch of providers

[omkar-foss]

Thanks a lot for looking into this @kaxil, and kudos @geraj1010 for this PR!

I've raised #44479 to use the warning block wherever applicable, so that we can show these prominent deprecation warnings consistently across Airflow docs. Cheers.

[geraj1010]

Thanks a lot for looking into this @kaxil, and kudos @geraj1010 for this PR!

I've raised #44479 to use the warning block wherever applicable, so that we can show these prominent deprecation warnings consistently across Airflow docs. Cheers.

My pleasure!

[geraj1010]

Greetings, I was away for the holidays. Thank you all for review!

@kaxil Thank you for resolving the conflict. Can you please tell me what it was?

[kaxil]

Greetings, I was away for the holidays. Thank you all for review!

@kaxil Thank you for resolving the conflict. Can you please tell me what it was?

Hi @geraj1010 , I hope you had a good holiday. Your base branch was 1000 commits behind the Airflow main -- Example: https://github.com/apache/airflow/commits/39ebd75c5cb066218a2b6b3940eddc217dd816d9/docs/sphinx_design/static/custom.css -- your branch's base commit was from December 2023 -- so rebased on the main branch.

[geraj1010]

Greetings, I was away for the holidays. Thank you all for review!
@kaxil Thank you for resolving the conflict. Can you please tell me what it was?

Hi @geraj1010 , I hope you had a good holiday. Your base branch was 1000 commits behind the Airflow main -- Example: https://github.com/apache/airflow/commits/39ebd75c5cb066218a2b6b3940eddc217dd816d9/docs/sphinx_design/static/custom.css -- your branch's base commit was from December 2023 -- so rebased on the main branch.

Ahh I see! I wonder how that happened? I've only started contributing in August 2024. Maybe I forked the repo incorrectly?