We just downloaded the Logsearch-for-cloudfoundry 210.3.1 but we had assumed this version pointed to latest firehose-to-syslog branch so we could use loggegrator v2 endpoints
The git submodule for firehose-to-syslog -- points to this commit not the develop branch like expected.
We noticed this problem when I had cloned this project and ran a test bosh-release because it did not look to be attaching to upstream develop, like the git submodules seemed to think.
We tried this --
git submodule update --init --recursive
This just pulled it but not the lates
git submodule foreach git pull origin develop
This was able to pull the submodule
…egrator v2 endpoints
We just downloaded the Logsearch-for-cloudfoundry 210.3.1 but we had assumed this version pointed to latest firehose-to-syslog branch so we could use loggegrator v2 endpoints
The git submodule for firehose-to-syslog -- points to this commit not the develop branch like expected.
https://github.com/cloudfoundry-community/firehose-to-syslog/tree/b88def89e19a52e9c00bc11494dfdf68244b6602 is from Oct 2018
We noticed this problem when I had cloned this project and ran a test bosh-release because it did not look to be attaching to upstream develop, like the git submodules seemed to think.
We tried this --
git submodule update --init --recursive
This just pulled it but not the lates
git submodule foreach git pull origin develop This was able to pull the submodule
This pull request includes that update...