Skip to content

Use api secret_key for airflow 3.0+ instead of webserver secret_key #52269

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 26 commits into
base: main
Choose a base branch
from

Conversation

albundy83
Copy link

@albundy83 albundy83 commented Jun 25, 2025

closes: #52267

Should resolve warning:

/home/airflow/.local/lib/python3.12/site-packages/airflow/configuration.py:858 DeprecationWarning: The secret_key option in [webserver] has been moved to the secret_key option in [api] - the old setting has been used, but please update your config.

Copy link

boring-cyborg bot commented Jun 25, 2025

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

  • Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
  • In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
  • Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
  • Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
  • Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
  • Be sure to read the Airflow Coding style.
  • Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
    Apache Airflow is a community-driven project and together we are making it better 🚀.
    In case of doubts contact the developers at:
    Mailing List: [email protected]
    Slack: https://s.apache.org/airflow-slack

@boring-cyborg boring-cyborg bot added the area:helm-chart Airflow Helm Chart label Jun 25, 2025
Signed-off-by: Grégoire Bellon-Gervais <[email protected]>
@albundy83 albundy83 changed the title Add api secret_key for 3.0+ instead of webserver secret_key Use api secret_key for 3.0+ instead of webserver secret_key Jun 26, 2025
@albundy83 albundy83 changed the title Use api secret_key for 3.0+ instead of webserver secret_key Use api secret_key for airflow 3.0+ instead of webserver secret_key Jun 26, 2025
@eladkal
Copy link
Contributor

eladkal commented Jun 30, 2025

tests are failing

@albundy83
Copy link
Author

tests are failing

Yes I see that.
I will try to understand why ...

@albundy83
Copy link
Author

@eladkal maybe this one will fix, can you allow another tests please ?

@albundy83
Copy link
Author

Ok new commits :)
I have this one that I don't understand why it fails ...
If someone can help me to understand

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:helm-chart Airflow Helm Chart
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Missing api secret_key capabilities to replace webserver for 3.0+
3 participants