added a new plugin that allows manipulation of extra_tags. Main use case
is to allow usage of same pipeline for both dev and prod setups but be able
to differentiate between messages and select a different path for your
dev stage (ex: route dev messages to local directory for examination rather
then production database)
Description
ExtraTags expert plugin aims to ease the testing of an existing pipeline and allow
easy routing of the messages in development phase. Main use case:
use extra_tags plugin right after a parser (or input) and mark the messages as
beloning to development stage json {'stage': 'dev'}
insert a prod-dev-routing decision right before final output and with filter
plugin route non-production messages to various backends to inspection
Testing
(.venv) ➜ intelmq git:(develop) ✗ pytest intelmq/tests/bots/experts/extra_tags -s
=========================================================================================================== test session starts ============================================================================================================
platform darwin -- Python 3.12.0, pytest-8.0.2, pluggy-1.4.0
rootdir: ws/extra-tags/intelmq
configfile: pytest.ini
plugins: cov-4.1.0, requests-mock-1.11.0
collected 5 items
intelmq/tests/bots/experts/extra_tags/test_expert.py ...True
..
---------- coverage: platform darwin, python 3.12.0-final-0 ----------
Coverage XML written to file coverage.xml
============================================================================================================ 5 passed in 2.01s =============================================================================================================
(.venv) ➜ intelmq git:(develop)
Description
ExtraTags expert plugin aims to ease the testing of an existing pipeline and allow easy routing of the messages in development phase. Main use case:
json {'stage': 'dev'}Testing