Configure a crawler_site_id by default. #106
Merged
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.
ftw.crawler now supports to configure a crawler_site_id. This change adds such a field for all solr cores by default. See 4teamwork/ftw.crawler#9
By adding the
crawler_site_id
field to the core template, all solr installation based on this buildout config will automatically receive the field for all cores, making it easier for developers to adapt to this feature.It isn't necessary to have the field on regulare cores, but it is easier to add it to all cores in ftw-buildouts than to add the field in each project separately.
config-version:
The
collective.recipe.solrinstance
does not properly update the configuration: it only reinstalls when values of its part change. When configurations of the cores change, those changes are not in the solrinstance part and thus the recipe does not reinstall and the change is not applied.As workaround we introduce a
config-version
value which is simply incremented and will trigger a reinstall of the solr part whenever incremented.