Skip to content
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

Requesting a silent mode for cf push command #1208

Closed
weymanf opened this issue Aug 21, 2017 · 3 comments
Closed

Requesting a silent mode for cf push command #1208

weymanf opened this issue Aug 21, 2017 · 3 comments

Comments

@weymanf
Copy link
Contributor

weymanf commented Aug 21, 2017

Command

cf push mynodeapp

What occurred

We are cf pushing an app as part of our deployment process. It runs inside of a bosh errand and it will fail because there is a limit to how much stdout it can read from an errand. The cf push using the nodejs buildpack emitted too many logs mostly containing the bundling of node modules.

Here is our bosh error.

Started running errand > push-apps/0. Failed: Response exceeded maximum allowed length (00:13:41)

Error 450001: Response exceeded maximum allowed length

I would list what the buildpack was logging out but I'm afraid it would be too long.

What you expected to occur

I just want to request for a silent mode for cf push where it will omit the " Building dependencies" step.

CLI Version

cf-cli_6.23.1_linux_x86-64.tgz

CC API Endpoint Version

2.84.0

Platform & Shell Details

Should be ubuntu.

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/150414724

The labels on this github issue will be updated when the story is started.

@dkoper
Copy link

dkoper commented Aug 22, 2017

Hi @weymanf

I feel the issue lies with the limitation on output from the errand (cloudfoundry-attic/bosh-lite#239 ?), not with the cf CLI.
We would not want to add a flag to cf push for such a corner case - every additional flag on push makes it more difficult to learn, use and maintain.

Regards,
Dies Koper
CF CLI PM

@weymanf
Copy link
Contributor Author

weymanf commented Aug 29, 2017

Okay thanks. Bosh has already fixed it on their side, but it's less frightening for people to upgrade a cli instead of an entire bosh director.

I'm going to close this issue. As putting a flag on the cli for this edge case is a little funky.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants