Enhancement: force hub index file update if hub data upgrade is forced #3124
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.
I ran into an issue by having a hub-index file younger than 24h within the docker container and needed to restart it while the hub holds newer data.
So this results in conflicting hashes for parsers loaded by a collection.
Setting the environment var
DO_HUB_UPGRADE
totrue
it just forces the already (old) indexed collections to upgrade, but not upgrading the index file.I think if someone forcing to get the newest data from the hub, than the local index should be as fresh as possible.
With this PR setting
DO_HUB_UPGRADE
totrue
also forces the local hub index to get updated on starting the docker container.