When OpenShift Online is crawled by a search engine or survey bot, we do not want to have such actions unidle gears, as this can significantly change our capacity needs. Currently, we have a modified version of restorer.php in place which does this, but the regex is hard-coded. We'll need to do some additional work to allow this to be configurable. (Jhon Honce had the suggestion of using an environment variable passed through httpd, to avoid having to read a file every time this script runs.)
Because this RFE is for OpenShift Online v2 and because you have a workaround, we don't see a need to prioritise this RFE for OpenShift Origin v2. However, we do plan to implement the feature in OpenShift Origin v3 (<https://trello.com/c/GV5xCQVL/9-5-unidle-from-routing-layer-traffic-ingress-idling>).
Miciah, I think you misunderstand. Our workaround specifically involves overriding a packaged file, and the next update will break us.
per discussion with agrimm, perhaps this can be implemented in the Apache config?
Andy, how long have you been running this workaround?
Removing needinfo on this. Our restorer has become even more highly customized over the past 8 months, but at this point we also haven't done any releases in 2016, so I'm not all that worried about this. we just have to immediately run puppet after any openshift package updates.
Thanks for the follow up Andy. I'm going to close this out then. I apologize that we never got around to this.