You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 5, 2020. It is now read-only.
Currently, when you have a task run for the current release ($task->runForCurrentRelease('xyz')) it will ALWAYS output the response from the command.
This becomes a problem when I want to do some "behind-the-scenes" variable building using these commands. For example, I am utilizing rocketeer to deploy my application to an AWS bastion server that then goes ahead and uploads the bundle to S3 for AWS CodeDeploy.
So if it takes 5 minutes for the deployment to complete, that huge json block shows every single time.
I suggest we add the ability to pass a (false by default) $silent parameter into $task->runForCurrentRelease() that will then go through and finally add $this->run($command, true). I will be submitting a PR for this shortly.
The text was updated successfully, but these errors were encountered:
Currently, when you have a task run for the current release (
$task->runForCurrentRelease('xyz')
) it will ALWAYS output the response from the command.This becomes a problem when I want to do some "behind-the-scenes" variable building using these commands. For example, I am utilizing rocketeer to deploy my application to an AWS bastion server that then goes ahead and uploads the bundle to S3 for AWS CodeDeploy.
So if it takes 5 minutes for the deployment to complete, that huge json block shows every single time.
I suggest we add the ability to pass a (false by default) $silent parameter into $task->runForCurrentRelease() that will then go through and finally add $this->run($command, true). I will be submitting a PR for this shortly.
The text was updated successfully, but these errors were encountered: