-
Notifications
You must be signed in to change notification settings - Fork 15.1k
Deserialize should work while retrieving variables with secrets backend #50880
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
Merged
amoghrajesh
merged 2 commits into
apache:main
from
astronomer:fix-secrets-backend-deser
May 21, 2025
Merged
Deserialize should work while retrieving variables with secrets backend #50880
amoghrajesh
merged 2 commits into
apache:main
from
astronomer:fix-secrets-backend-deser
May 21, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kaxil
reviewed
May 21, 2025
kaxil
approved these changes
May 21, 2025
eladkal
approved these changes
May 21, 2025
ashb
reviewed
May 21, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does {{ var.json.myvar }}
still work as it did before?
@ashb yeah it works like it used to. Tried with:
Output:
|
Unrelated failures, merging. |
nailo2c
pushed a commit
to nailo2c/airflow
that referenced
this pull request
May 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:task-sdk
backport-to-v3-0-test
Mark PR with this label to backport to v3-0-test branch
type:bug-fix
Changelog: Bug Fixes
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes: #50666
Problem
As reported in #50666,
deserialize_json
option wasn't working when trying to use it with Variable.get with AWS secrets manager.But this problem on further investigation revealed to be not just for AWS secrets backend but a bug in the
Variable
module itself. The bug didn't honor thedeserialize_json
flag at all when it was passed for secrets backend which shouldn't be the case at all.To prove this, did the following:
Set up a
airflow.secrets.local_filesystem.LocalFilesystemBackend
and checked with both Airflow 2 and Airflow 3.var.json
Dag used:
Airflow 2:
Airflow 3:
As observed the second print for Airflow 3 is a string when it should really be a dictionary.
Testing
Set up a
airflow.secrets.local_filesystem.LocalFilesystemBackend
and checked with both Airflow 2 and Airflow 3.var.json
And exporting these variables in init.sh of breeze:
Dag used:
Before changes:
After changes:
^ 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.