Skip to content

Conversation

@bugraoz93
Copy link
Contributor


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

@bugraoz93 bugraoz93 force-pushed the add-dummy-fernet-key-to-integration-tests branch 2 times, most recently from c387fc5 to 043f081 Compare November 9, 2025 18:38
@jscheffl
Copy link
Contributor

jscheffl commented Nov 9, 2025

As via slack: I think we should discuss first how we handle this not to have security side-effects

@potiuk
Copy link
Member

potiuk commented Nov 9, 2025

Yeah. I think yeah - we should get some good agreement, but for now setting the key seem a good idea ?

@potiuk potiuk added full tests needed We need to run full set of tests for this PR to merge all versions If set, the CI build will be forced to use all versions of Python/K8S/DBs labels Nov 9, 2025
@potiuk potiuk force-pushed the add-dummy-fernet-key-to-integration-tests branch from 043f081 to 3df0ad5 Compare November 9, 2025 19:48
@potiuk
Copy link
Member

potiuk commented Nov 9, 2025

Added version/tests labels.

@bugraoz93 bugraoz93 force-pushed the add-dummy-fernet-key-to-integration-tests branch 2 times, most recently from 0a742d6 to ef14b13 Compare November 12, 2025 07:33
@bugraoz93 bugraoz93 force-pushed the add-dummy-fernet-key-to-integration-tests branch from ef14b13 to 6f4db09 Compare November 15, 2025 23:35
@bugraoz93 bugraoz93 force-pushed the add-dummy-fernet-key-to-integration-tests branch from 6f4db09 to faf79d2 Compare November 15, 2025 23:37
Copy link
Contributor

@jscheffl jscheffl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For me this looks good now!

Even once merged could we still start re-considering dropping the NullFernet? (Otherwise print a BIIIIG Banner if used...

 ___________________
< Big Banner, yeah! >
 -------------------
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||

@potiuk
Copy link
Member

potiuk commented Nov 16, 2025

 ___________________
< Big Banner, yeah! >
 -------------------
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||

Yes. Why not... But we already have another candidate for that banner - avoiding COW when forking ... #58365 (cc: @wjddn279 )

@bugraoz93
Copy link
Contributor Author

I agree. We should definitely have it where we can for sure reconsider. I will nudge people for another round and will start a lazy consensus on it while creating those follow-ups :)

@potiuk potiuk merged commit d601be8 into apache:main Nov 17, 2025
201 checks passed
aaron-wolmutt pushed a commit to aaron-wolmutt/airflow that referenced this pull request Nov 20, 2025
* Add dummy Fernet key for integration tests

* dynamic fernet key generation from devel-common

* Add pyyaml dependency and update YAML loading method in fernet.py

* Revert integration test changes

* Update integration tests to use always the same generated Fernet key from environment variable
Copilot AI pushed a commit to jason810496/airflow that referenced this pull request Dec 5, 2025
* Add dummy Fernet key for integration tests

* dynamic fernet key generation from devel-common

* Add pyyaml dependency and update YAML loading method in fernet.py

* Revert integration test changes

* Update integration tests to use always the same generated Fernet key from environment variable
itayweb pushed a commit to itayweb/airflow that referenced this pull request Dec 6, 2025
* Add dummy Fernet key for integration tests

* dynamic fernet key generation from devel-common

* Add pyyaml dependency and update YAML loading method in fernet.py

* Revert integration test changes

* Update integration tests to use always the same generated Fernet key from environment variable
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

all versions If set, the CI build will be forced to use all versions of Python/K8S/DBs full tests needed We need to run full set of tests for this PR to merge kind:documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants