Ensure that Cerebro opsfile uses correct route_registrar job #145
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Logsearch Bosh Release team,
It looks like you forgot to update the Cerebro opsfile when switching the
route_registrar
job to use the routing release. This PR updates the cerebro.yml opsfile to use the correct release, matching the cloudfoundry.yml opsfile. I've verified that manifests generated with the updated opsfile work as expected and fix theError: Job 'route_registrar' not found in Template table
error you get when it uses the previouslogsearch-for-cloudfoundry
release.cheers,
Pete