AnsweredAssumed Answered

Content Control Utility v3 by CP Code process time?

Question asked by Yuta Suwa on Aug 14, 2017
Latest reply on Aug 16, 2017 by Yuta Suwa



Is the estimatedSeconds values returned from v3 reliable?

I tried it by httpie and returned response as below:


$ http -v --auth-type edgegrid -a default: :/ccu/v3/delete/cpcode/production objects:='[******]'

POST /ccu/v3/delete/cpcode/production HTTP/1.1
Accept: application/json, */*
Accept-Encoding: gzip, deflate


HTTP/1.1 201 Created
Allow: POST
Connection: keep-alive
Content-Length: 268
Content-Location: /ccu/v2/purges/0c6...<SNIP>

Content-Type: application/json


"detail": "Request accepted.",
"estimatedSeconds": 240,
"httpStatus": 201,
"pingAfterSeconds": 240,

"progressUri": "/ccu/v2/purges/0c6...<SNIP>




It seemingly processed via v2 and can validate progress through v2 purge status.

those responses are different from CCU API Resources "Delete by CP Code" example like;

{     "purgeId": "e535071c-26b2-11e7-94d7-276f2f54d938",     "estimatedSeconds": 5,     "httpStatus": 201,     "detail": "Request accepted",     "supportId": "17PY1492793544958045-219026624" }

Did I missed something or misunderstand v3 CP Code purge functionality?