Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimisation on -d option #29

Open
LtSich opened this issue Jun 28, 2021 · 0 comments
Open

Optimisation on -d option #29

LtSich opened this issue Jun 28, 2021 · 0 comments

Comments

@LtSich
Copy link

LtSich commented Jun 28, 2021

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant