ENH: new parameter autoupdate_cached_database

[sebix]

New parameter autoupdate_cached_database to disable automatic updates (downloads) of cached databases

[codecov-commenter]

Codecov Report

Merging #2180 (e4b20d7) into develop (ce60fd4) will increase coverage by 0.00%.
The diff coverage is 33.33%.

@@           Coverage Diff            @@
##           develop    #2180   +/-   ##
========================================
  Coverage    76.34%   76.34%           
========================================
  Files          441      441           
  Lines        23649    23654    +5     
  Branches      3739     3739           
========================================
+ Hits         18055    18059    +4     
  Misses        4857     4857           
- Partials       737      738    +1     

Impacted Files	Coverage Δ
intelmq/bots/experts/asn_lookup/expert.py	35.20% <33.33%> (+0.52%)	⬆️
intelmq/bots/experts/domain_suffix/expert.py	43.33% <33.33%> (+0.63%)	⬆️
intelmq/bots/experts/maxmind_geoip/expert.py	21.42% <33.33%> (+0.62%)	⬆️
...telmq/bots/experts/recordedfuture_iprisk/expert.py	42.55% <33.33%> (+0.61%)	⬆️
intelmq/bots/experts/tor_nodes/expert.py	47.05% <33.33%> (+0.63%)	⬆️
intelmq/bots/experts/ripe/expert.py	76.53% <0.00%> (-1.03%)	⬇️

[waldbauer-certat]

We should maybe consider cronjobs instead of integrating update mechanisms into intelmq bots. but seems fine for me

[sebix]

We should maybe consider cronjobs instead of integrating update mechanisms into intelmq bots. but seems fine for me

Funny that you suggest that.
cron is a (deprecated) tool to schedule program starts. We use it for exactly this purpose (see https://github.com/certtools/intelmq/tree/develop/contrib/cron-jobs etc.)
And instead of having a set of shell scripts downloading the databases @gethvi migrated the update code to the bots which has major advantages, e.g. the update scripts are aware of the settings of the bots (license keys, database locations) and can also check if the bots are configured. The updates code is also located directly at the same place as the code using it and future improvements could include automated database-updates not relying on cron, but on internal timers (I image that a fully dockerized setup will need that due to the lack of third-party components in the minimalistic container)
See #1524 and https://github.com/certtools/intelmq/blob/version-3.0-ideas/docs/architecture-3.0.md#user-content-general-principles and you can find further reasoning in the CEF-2018-AT-IA-0111 reports and at other places.