Milan
Milan
@mukuldeepfence I see successfully delete message on enterprise branch, Do you have credentials to test on kafka-rest branch, I see there is no difference in terms of code:
Got 500 internal server error on threatmapper kafka-rest branch: curl 'https://167.71.236.9/deepfence/v1.5/docs/delete' \ -H 'authority: 167.71.236.9' \ -H 'accept: application/json, text/javascript' \ -H 'accept-language: en-GB,en-US;q=0.9,en;q=0.8' \ -H 'authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJmcmVzaCI6ZmFsc2UsImlhdCI6MTY3MTExODY0NiwianRpIjoiMDcwMzc5Y2UtM2U4Mi00MjgxLTg5MzYtMjE1OTEyNWE4YWMwIiwidHlwZSI6ImFjY2VzcyIsInN1YiI6eyJpZCI6MSwiZmlyc3RfbmFtZSI6Im0iLCJsYXN0X25hbWUiOiJtIiwiZW1haWwiOiJtQGQuaW8iLCJjb21wYW55IjoiZCIsInJvbGUiOiJhZG1pbiIsImFwaV9rZXkiOiJmZDI4ZDlhZC1kODM2LTRmZTktOGM2Yy01M2M4YjUyZjFkNDciLCJpc0FjdGl2ZSI6dHJ1ZSwiY29tcGFueV9saWNlbnNlX2V4aXN0cyI6dHJ1ZX0sImV4cCI6MTY3MTIwNTA0Nn0.Utj5iiNyuFTERC6GaPQ-7iHtVvkLwnVGp4aRwskaY1wP357TgH0YK9cxSX3eRh2w9q7OxsoT32hqkdszRSU4lP8ssbgGJVuFlEsjemtf6WRhSGBYgKS6ODNGKAcoZDlTqPAD3slNfieUA4ZSLuQch8buULh9ctI5pKsl2Oz3NkOHlVcOoBJ0i46HQ4bjfpyNr0v3eDEr83U8rdr_mBbqkziv4vu3n_kyQG-06FrVMUooBzYPmhKhaWun8xWSiJeyTZe1lims8CwaXYp11WU_CmrQHf6-V6pzZ9z26VbUwwyVY-4noOx1QZF4JIlUrYk2WekcUqode9jla1OJbpLAUA' \...
Fixed in: https://github.com/deepfence/ThreatMapper/pull/1353
We did UI sorting for now: https://github.com/deepfence/ThreatMapper/pull/1379/files#diff-14f8a387803e2045aedaddaac3ed071e4263a97cf3c8d27ead74f525e988abd3
May be similar issue with: https://github.com/deepfence/ThreatMapper/issues/1348
Yes with order it works
I saw an issue in image syncing where node id which has @ and . character fails to use api path: node_id: [email protected] and failed api is :
This is fixed in: https://github.com/deepfence/ThreatMapper/pull/1325
API request for start scan of image tag for instance: { "filters": { "cloud_account_scan_filter": { "filter_in": null }, "container_scan_filter": { "filter_in": null }, "host_scan_filter": { "filter_in": null }, "image_scan_filter": {...
Animation works but there is an issue of using it in the App because useFetcher still holds previous state.