-
Notifications
You must be signed in to change notification settings - Fork 15.3k
Add new breeze run
command for non-interactive command execution
#52370
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
Conversation
Add a new `breeze run` command that allows running commands in the Breeze environment without entering an interactive shell. This is useful for automated testing, and one-off command execution which is useful for AI too.
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.
Nice :)
…execution (#52370) Add a new `breeze run` command that allows running commands in the Breeze environment without entering an interactive shell. This is useful for automated testing, and one-off command execution which is useful for AI too. (cherry picked from commit bb041b3) Co-authored-by: Kaxil Naik <[email protected]>
Nice ... But this has already been possible with breeze shell :) |
Or even with default |
You just needed to separate command with
But yeah - run is more explicit and nicer as you can pass regular parameters - no need to quote command. |
…execution (#52370) (#52373) Add a new `breeze run` command that allows running commands in the Breeze environment without entering an interactive shell. This is useful for automated testing, and one-off command execution which is useful for AI too. (cherry picked from commit bb041b3) Co-authored-by: Kaxil Naik <[email protected]>
Very nice change @kaxil -> ❤️ |
Add a new
breeze run
command that allows running commands in the Breeze environment without entering an interactive shell. This is useful for automated testing, and one-off command execution which is useful for AI too.^ 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.