YoannAbriel opened a new pull request, #63343:
URL: https://github.com/apache/airflow/pull/63343
After migrating from Airflow 2.x with a different Fernet key, encrypted
variables fail to decrypt — `Variable.get_val()` returns `None`. The
`VariableResponse` Pydantic model has `val: str` which rejects `None`, so both
`GET /variables` and `GET /variables/{key}` blow up with a 500
`PydanticSerializationError`.
Changed `val` field type from `str` to `str | None` in `VariableResponse`.
The existing `redact_val` validator already handles `None` correctly (early
return).
Added two tests that insert a variable with a garbage encrypted value and
verify both the single-get and list endpoints return 200 with `value: null`.
Closes: #63341
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Code (Opus 4, claude-opus-4-6)
Generated-by: Claude Code (Opus 4, claude-opus-4-6) following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#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](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
