Previous community decisions are not removed on pull

[blotus]

When we perform a community blocklist pull, IPs from the previous pull are not removed. This leads to many IPs staying in the database even though they were not pulled again.
While you are guaranteed to get the deleted IPs, you are not guaranteed to always receive the same IPs to block, and the decisions will keep pilling up in the database until they expire.
The same thing can happen when uninstalling a scenario, you will keep the community decisions related to it until they expire, while you are no longer interested in them

A pull should clean the previous decisions so that the database only contains the content from the last pull.

[github-actions]

@blotus: Thanks for opening an issue, it is currently awaiting triage.

In the meantime, you can:

1. Check Crowdsec Documentation to see if your issue can be self resolved.
2. You can also join our Discord.
3. Check Releases to make sure your agent is on the latest version.

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]

@blotus: There are no 'kind' label on this issue. You need a 'kind' label to start the triage process.

• /kind feature
• /kind enhancement
• /kind refactoring
• /kind bug
• /kind packaging

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.