Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Doesn't handle durable function 202 response with large number of zones

See original GitHub issue

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

Add a number of DNS zones that your SP has access to, mine has 27
Open developer tools
Monitor the call to /api/dns-zones
It may return a 202 accepted response instead of 200 with a url to fetch the result

In my case the response was:

{
  "id": "******",
  "statusQueryGetUri": "https://******.azurewebsites.net/runtime/webhooks/durabletask/instances/********?taskHub=DurableFunctionsHub&connection=Storage&code=******==&returnInternalServerErrorOnFailure=true",
  "sendEventPostUri": "https://********.azurewebsites.net/runtime/webhooks/durabletask/instances/******/raiseEvent/{eventName}?taskHub=DurableFunctionsHub&connection=Storage&code=********==",
  "terminatePostUri": "https://********.azurewebsites.net/runtime/webhooks/durabletask/instances/******/terminate?reason={text}&taskHub=DurableFunctionsHub&connection=Storage&code=********==",
  "purgeHistoryDeleteUri": "https://acmedcdcftappsprod.******.net/runtime/webhooks/durabletask/instances/********?taskHub=DurableFunctionsHub&connection=Storage&code=********==",
  "restartPostUri": "https://********.azurewebsites.net/runtime/webhooks/durabletask/instances/******/restart?taskHub=DurableFunctionsHub&connection=Storage&code=******=="
}

and the response from the durable task status query url was wrapped like so:

{
  "name": "GetDnsZones_Orchestrator",
  "instanceId": "***",
  "runtimeStatus": "Completed",
  "input": null,
  "customStatus": null,
  "output": [
    "my-zone",
    "x27...",
  ],
  "createdTime": "2021-06-01T10:08:14Z",
  "lastUpdatedTime": "2021-06-01T10:09:18Z"
}

Environment (please complete the following information):

Certificate Type: [e.g. Zone Apex, Sub-domain, Wildcard]
Certificate Deploy Target: [e.g. App Service]

Additional context Add any other context about the problem here.

Issue Analytics

State:
Created 2 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

shibayancommented, Jun 3, 2021

I have not implemented it to handle 202, but you can create a pull request to improve it. Alternatively, it is recommended that you use the REST API to issue certificates.

0reactions

timjacommented, Jun 3, 2021

Thanks will see how we go, may come back later with a PR.

In general it works fine, but when I raised this issue I tried a few times over a 30minute period and I wasn’t able to get it to load