Logging output errors with CF_TRACE=true cf enable diego

[Tom Shacks]

dependencies

may be similar to #3

tom$ cf -v
cf version 6.22.1+6b7af9c-2016-09-24

Diego-Enabler v1.2.1

CF version 240

issue

when running CF_TRACE=true cf enable-diego <app> you get the following error

FAILED
Error: unexpected end of JSON input

however, the command succeeds, because running cf has-diego-enabled <app> afterwards returns true and i have indeed checked that the app is running on a cell and not a dea.

this is an issue because it means the command exits 1.

just to be clear, running cf enable-diego <app> without CF_TRACE=true before it succeeds and exits 0.

thanks!

[cf-gitbot]

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

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

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

[Dies Koper]

The team told me the issue indeed only occurs when CF_TRACE is enabled, and there is no easy way to fix this. Are you OK to keep using it without the trace enabled?

[Tom Shacks]

Yes we'll do our best :)

Do you know roughly when it might be fixed?

Thanks

[Dies Koper]

When we run out of other important things to do or when we start revamping the plugin architecture. Maybe in 3 months?

[Tom Shacks]

Okay thank you!

[Dies Koper]

I have added this to the known issues list, with tested work-arounds.
Closing this issue as we're not likely to get to addressing this in a reasonable timeframe.
Thanks again for reporting the issue.

Regards,
Dies Koper
CF CLI PM