crowdsec icon indicating copy to clipboard operation
crowdsec copied to clipboard

Enhancement: force hub index file update if hub data upgrade is forced

Open nox-x opened this issue 1 year ago • 4 comments

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 to true 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 to true also forces the local hub index to get updated on starting the docker container.

nox-x avatar Jul 11 '24 14:07 nox-x

@nox-x: There are no 'kind' label on this PR. You need a 'kind' label to generate the release automatically.

  • /kind feature
  • /kind enhancement
  • /kind refactoring
  • /kind fix
  • /kind chore
  • /kind dependencies
Details

I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

github-actions[bot] avatar Jul 11 '24 14:07 github-actions[bot]

@nox-x: There are no area labels on this PR. You can add as many areas as you see fit.

  • /area agent
  • /area local-api
  • /area cscli
  • /area appsec
  • /area security
  • /area configuration
Details

I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

github-actions[bot] avatar Jul 11 '24 14:07 github-actions[bot]

/kind enhancement /area configuration

nox-x avatar Jul 11 '24 14:07 nox-x

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 49.87%. Comparing base (1b01041) to head (89142ac). Report is 1 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff             @@
##           master    #3124       +/-   ##
===========================================
+ Coverage   32.05%   49.87%   +17.82%     
===========================================
  Files         320      321        +1     
  Lines       37662    37664        +2     
===========================================
+ Hits        12073    18786     +6713     
+ Misses      24287    17055     -7232     
- Partials     1302     1823      +521     
Flag Coverage Δ
bats 38.47% <ø> (?)
unit-linux 34.42% <ø> (ø)
unit-windows 29.06% <ø> (+0.01%) :arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

codecov[bot] avatar Jul 11 '24 15:07 codecov[bot]