Ruben Koster
Ruben Koster
Once CI is green again @ramonskie is gonna look at this (as discussed during working group meeting).
@beyhan any news on the security front?
Thanks! @haydonryan
@svrc as the author of the original PR, do you happen to remember the reasoning behind the current logic?
Let's go with the current implementation and add percentage-based and min host settings later if we receive feedback that the current behavior does not work for people. Let's get some...
It seems like you are upgrading from an ancient version of Postgres. This issue was fixed here: https://github.com/cloudfoundry/bpm-release/pull/152
Updating BPM would still be an update of the instance, and as such have a change of an improper Postgres shutdown. @bgandon do you remember if there was a workaround...
This PR probably also needs to align with package spec based approach: https://github.com/cloudfoundry/bosh-cli/pull/696#issuecomment-3437670344
As @jpalermo mentioned above you could detach the disk an look at the logs from an other VM, instructions for this can be found here: https://bosh.io/docs/tips/#unresponsive-vm-logs (from step 3 onwards).
In general I don't like the ux of passing a flag, It would be better to be able to disable compression through the package spec file. This gives more fine-grained...