Python durable funtion in kubernetes, baseUri of the management api payload cannot be configured

[realsenseme]

Hi All,

I have a durable function app with kubernetes as deployment target. Function runtime is python.

Found Python version 3.9.6 (python3).

Azure Functions Core Tools
Core Tools Version:       3.0.3568 Commit hash: e30a0ede85fd498199c28ad699ab2548593f759b  (64-bit)
Function Runtime Version: 3.0.15828.0

If I trigger one of the registered orchestrator as below, the response with management apis has the baseUri with a missing path segment. (highlighted in green on the trigger url)

How is the baseUrl evaluated and is there a way to configure the baseUri or atleast exclude the baseUrl and have only relative paths starting from /runtime in the response payload?

Any inputs is highly appreciated :)

regards

[davidmrdavid]

Hi @realsenseme,

Thanks for reaching out!

Can you clarify what you mean by "the response management APIs has the baseURI with a missing path segment"? Is it that you expect to see a /pydurable-http/ segment in them?

Also, do the links you receive 404 on a GET request, or do they work as-is?

Finally, and just for context, what version of azure-functions-durable are you using? Similarly, are you on extensionBundles v1 or v2? thanks!

[realsenseme]

@davidmrdavid Let me answer the questions first: azure-functions-durable : version 1.0.3
extensionBundle : v2

In the meantime I have tried a few things on my side and I can adjust the durabletask client response manually. but this is not we are looing for.

To clarify my question further, I will explain my situation once more:

We are deploying the durable function in AKS with AppGw and Applicaiton Gateway Ingress controller to control incoming traffic where we are handling SSL termination.

And the ingress object to the durable client looks like this:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: "pydurable-http"
  annotations:
    kubernetes.io/ingress.class: azure/application-gateway
    appgw.ingress.kubernetes.io/appgw-ssl-certificate: default
    appgw.ingress.kubernetes.io/ssl-redirect: "true"
    appgw.ingress.kubernetes.io/backend-path-prefix: "/"
  labels:
    app: "pydurable-http"
spec:
  rules:
    - host: "<somethost>"
      http:
        paths:
          - path: /pydurable-http/*
            pathType: ImplementationSpecific
            backend:
              service:
                name: "pydurable-http"
                port:
                  number: 80

The management APIs are by default having a context path : {host}/runtime/webhooks/....

Is it possible to configure the baseUrl for the runtime to be something like : {host}/pydurable-http/runtime/webhooks/.... so that they are accessible outside the cluster? If so where can I configure?

Thanks in advance for your support!

[davidmrdavid]

@cgillum, do you have any context on this? Is it possible to modify the baseUrl? Thanks!

[cgillum]

@realsenseme What is the code you're using to generate this payload? For example, are you using the create_check_status_response method? If so this is the code used to update our URL templates with the origin of the request (unfortunately I don't have enough Python experience to tell you for sure whether it would preserve the full path).

[realsenseme]

@cgillum Thanks for the response. _replace_url_origin does preserve the full path and the management api path picks up the baseUrl from the requestUrl.

But that does not modify anything for the runtime api path.

For example: I want my function api path to be

  "extensions": {
    "http": {
      "routePrefix": "pydurable-http/api"
    }
  }

My orchestrator trigger looks like:

GET http://localhost:7071/pydurable-http/api/orchestrators/PyDurableOrchestrator

And the response is:

{
  "id": "6dbb0630997a44509726edd077ad9ff3",
  "statusQueryGetUri": "http://localhost:7071/runtime/webhooks/durabletask/instances/6dbb0630997a44509726edd077ad9ff3?taskHub=TestHubName&connection=Storage&code=5kvDtr56aYk8rAuDLW9Y53CBfabstBJ1ZtWJDGCNA6TDRnxaXxRY2A=="
}

Is there any way I can also configure the /runtime/webhooks also to have the context path http://localhost:7071/pydurable-http/runtime/webhooks/... ?

[ConnorMcMahon]

To my knowledge, the /runtime/webhooks/durabletask endpoint is not customizable.

The good news is that all of these HTTP endpoints are essentially just prebuilt APIs that call the durable client. You can create your own custom HTTP triggers that implement the actions you need. With HTTP triggers, you have a lot more control over the api endpoints, as you have found in your other post already.

Then, instead of using create_check_status_response, you can create your own helper function that creates a payload that routes to your http triggers instead.

It's a bit more work, but then you have full control over the endpoints as opposed to our fixed APIs.

[realsenseme]

@ConnorMcMahon This was the next logical thing that worked. But for our arrangement, to have a wrapper which builds the response payload works but not preferred. I was able to configure this at my reverse proxy by configuring the ingress and that works better with less work. Thanks everyone for the help :) . It would still be nice and handy if we had an option to configure the context path for runtime apis.

[ConnorMcMahon]

Appreciate the feedback. We will consult with the Azure Functions host team, as they are the ones who provide us with these webhook endpoints to see if they could make those configurable.