Optimisation on -d option #29
Description
Same problem that we get with the -s option.
We should get differents options
-d : try to clear everything
-d --zone=zone_id : try to remove everything about that zone
-d --account=account_id : try to remove everything for that account
-d --token=token_id : try to remove everything that use that token.
The goal for those option is to quickly adapt the configuration without the need to make a lot of request to CF.
Like if we remove only 1 zone on CF side, to being able to remove that zone only from the local cache (and try to clean that zone on CF).
I have start a -d 30 minutes ago... I quickly get information about existing list, and now nothing happen...
I will continu to wait, but I will probably need to build my own script to clear everything on CF side...
This was 30min ago...
INFO[28-06-2021 15:00:56] ip list crowdsec_block already exists account_id=xxxxxxxx
INFO[28-06-2021 15:00:56] ip list crowdsec_block already exists account_id=xxxxxxxx