Sam Leung

@SpencerBrown Are there any progress to get this change merged upstream? I would like to see this merged as well. @apparentlymart @vancluever what's holding up this enhancement?

@janosbinder ~~is there a way to get the provider to print out the api calls used?~~ To print out the output to standard out: ``` export TF_LOG=debug ``` In my...

Hi @mogul, If I understand correctly, you could potentially simplify the process by using a data block to read the ID of the service instance and binding it to the...

Yes, this is still an issue when deploying large artifacts, especially in the case of nodejs artifact with all node_modules bundled together as one single deployable unit.

I can reproduce this issue with purelb as well.

One quick way to fix this is to use --retry-all-errors instead of --retry https://stackoverflow.com/questions/10285700/curl-error-recv-failure-connection-reset-by-peer-php-curl#:~:text=One%20way%20we%20can%20avoid,number%20of%20worker_connections%20in%20nginx.

I added service route binding to here: https://github.com/cloudfoundry-community/terraform-provider-cloudfoundry/pull/577 It uses the go-cfclient, so we don't have to update the cf-cli fork anymore

@Cocossoul I'd say make sense to have this default to 0, and only enable for the applications needing the extra time. However, I have one concern, the applications should not...

Is this still necessary? Since 1.184.0 already fixed this and the reported status should now be "STOPPING" rather than "STOPPED", the wait loop will block until the app status gets...

Another note, the provider does not actually perform the unbind operations on the stopped app. The unbind operation is done by the CF controller itself. The bluegreen_strategy make these calls...