-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
Allow variables to be printed to STDOUT #31851
Labels
Comments
vedantlodha
added
kind:feature
Feature Requests
needs-triage
label for new issues that we didn't triage yet
labels
Jun 12, 2023
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval. |
vedantlodha
changed the title
Allow
Allow variables to be printed to STDOUT
Jun 12, 2023
airflow variables export -
to Output to stdout
If the folks think this is a valid request, i would like to work on this. I kinda have a draft patch ready for this. |
Feel free. Sounds like a good first contribution |
phanikumv
added
good first issue
and removed
needs-triage
label for new issues that we didn't triage yet
labels
Jun 12, 2023
Assigned it to you @vedantlodha |
vedantlodha
added a commit
to vedantlodha/airflow
that referenced
this issue
Jun 20, 2023
Similar to connections, this change allows the cli to export the variables to the stdout using 'airflow variables export -' Fixes apache#31851
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Currently, the
airflow variables export
command requires an explicit file path and does not support output to stdout. However connections can be printed to stdout usingairflow connections export -
. This inconsistency between the two export commands can lead to confusion and limits the flexibility of the variables export command.Use case/motivation
To bring some consistency, similar to connections, variables should also be printed to STDOUT, using
-
instead of filename.Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: