Process contract/token webhooks

[Uxio0]

Contract and token webhooks should be processed invalidating contract/token cache when transaction service starts sending them.

Related to safe-global/safe-transaction-service#1082

[fmrsabino]

For invalidating all the contracts cache this is already possible by doing something like:

curl --location --request POST 'https://localhost:8080/v2/flush' \
--header 'Content-Type: application/json' \
--data-raw '{
    "invalidate": "Contracts"
}'

And for invalidating the token related cache you can do the following:

curl --location --request POST 'https://[safe-client.staging.gnosisdev.com](localhost:8080)/v2/flush' \
--header 'Content-Type: application/json' \
--data-raw '{
    "invalidate": "Tokens",
    "pattern_details": {
        "chain_id": "4"
    }
}'

[Uxio0]

Sure @fmrsabino , but I was talking about processing webhooks the same way we do it with new transactions or new confirmations, not using admin endpoints 😉

[fmrsabino]

Sure @fmrsabino , but I was talking about processing webhooks the same way we do it with new transactions or new confirmations, not using admin endpoints 😉

I don't think these are considered admin endpoints. The Config Service uses these for the hooks. But if we want to change that we can discuss!

[fmrsabino]

Closing this issue as it no longer applies in this context. But we can open a new discussion under https://github.com/safe-global/safe-client-gateway-nest if it makes sense.