Andy Lo-A-Foe
Andy Lo-A-Foe
@crsimmons what we are actually seeing is that most version of the `CF CLI` are not opening a `websocket` connection but are rather polling the API for logs with a...
@chombium thanks for your detailed explanation. We have indeed positioned `cf logs` as a tool for debugging only for our developers on our platform. However, it has become extremely unreliable...
I wanted to rename the `Proxy` field to `Bastion` but this will break compatibility. I hope to improve coverage as well.
Yep, will look into resolving conflicts shortly
@remyleone using Go 1.18? If so, see #271
@ttreptow nice! confirmed the crashes are gone with Go 1.18.2 -- after upgrading tools to v0.1.11
@AndrewPentsak this should be addressed in the [ongoing work on migrating to the v3 API](https://github.com/cloudfoundry-community/terraform-provider-cloudfoundry/pull/417), it's still in WIP for now.
I did some investigation on this and when this happens the `v2` API indeed returns the new image. Currently the provides uses this as the source of truth. When using...
Switching to the v3 API fully means rewriting most of the provider I'm afraid. The `UnknownError` should probably be handled more gracefully by the deploy strategy. Are you using `blue-green`...
The `v3` API supports this, example: https://github.com/cloudfoundry-community/cloudfoundry-cli/blob/d6a4525baeca819ac1d1b69d36f86f648d2fd9b3/api/cloudcontroller/ccv3/process.go#L155-L162 adding support for this while still primarily using the `v2` would be the challenge