Handle discrepancy between e/w and gc logsearch

[jmcarp]

Logsearch in e/w is using our fork of logsearch-for-cloudfoundry and an old version of logsearch-boshrelease (v200). Logsearch in gc almost the same as logsearch-for-cloudfoundry upstream (just waiting for a small patch to be merged) and the latest release of logsearch-boshrelease (v203). To keep maintenance simple, we may want to update e/w logsearch to match gc. But because the elasticsearch mappings and logstash filters have changed since we forked logsearch-for-cloudfoundry, we'd have to re-process our existing logs for this to work. So we have two options, neither of which seems great:

• Update e/w to the latest releases and migrate our existing logs
• Run different versions of logsearch until e/w goes away

Even though it would be ideal to keep parity between environments, I think we should make an exception in this case. The migration wouldn't be too complicated in theory, but lots of things could go wrong, and I'm not sure it's a good use of time. I think it would be simpler to make a temporary e/w branch and change it as little as possible between now and the end of e/w.

@LinuxBozo @sharms

[LinuxBozo]

👍 to Just doing branch for e/w