Unable to use Resolver Policy in a Graphql Resolver for POST http calls

Question

Unable to use Resolver Policy in a Graphql Resolver for POST http calls

Freddy Martinez Garcia 0

Hi guys

I have an API Management service with a Synthetic Graphql API. There, I'm trying to configure my mutations. Resolvers for this mutations are implemented in Azure Functions with the HttpTrigger, meaning that we need to call them by a HTTP call.

We tried with a GET method it works perfect, but we don't like the idea of calling our mutations by a GET request, we want to use a POST request.

My graphql schema looks like this:

schema {
  query: Query
  mutation: Mutation
}

type Mutation {  
	SendChatTextMessage(input: SendChatTextMessageInput!): SendChatMessageResp
}

	GetUserChatMessages(userId: UUID!): [ChatTextMessage]
}
input SendChatTextMessageInput {  
	messageId: UUID!  
	senderUserId: UUID!  
	receiverUserId: UUID!  
	messageContent: String!
}
enum Language {  
	ENGLISH,  
	SPANISH
}
enum ChatMessageSendStatus {  
	SUCCESS, 
	FAIL
}
type ChatMessageErrorData {  
	code: Int  
	message: String
}
type SendChatMessageResp {  
	messageId: UUID!  
	status: ChatMessageSendStatus!  
	error: ChatMessageErrorData
}
type ChatTextMessage {  
	messageId: UUID!  
	senderUserId: UUID!  
	receiverUserId: UUID!  
	messageContent: String!
}

and I defined my Resolber policy like this:

<http-data-source>
    <http-request>
        <set-method>POST</set-method>
        <set-url> [My Azure Function URL] </set-url>
        <set-header name="Content-Type" exists-action="override">
            <value>application/json</value>
        </set-header>
        <set-body>@{
            var args = context.Request.Body.As<JObject>(true)["arguments"];  
            JObject jsonObject = new JObject
            {
                new JProperty("input",
                    new JObject
                    {
                        new JProperty("messageId", args["input"]["messageId"]),
                        new JProperty("senderUserId", args["input"]["senderUserId"]),
                        new JProperty("receiverUserId", args["input"]["receiverUserId"]),
                        new JProperty("messageContent", args["input"]["messageContent"])
                    }
                )
            };
            return jsonObject.ToString();
        }</set-body>
    </http-request>
</http-data-source>

when I try to run my mutation, I get the error: Could not test the resolver policy. Please try again later.

Can someone tell me if you have done this before? Cause in this post I saw that it's a known issue from 2022, but I'm not sure if this has been fixed by Microsoft or not.

Any help here please?

Ben Gimblett 4,560 Reputation points Microsoft Employee

2023-11-24T15:21:34+00:00

Hi - I've tried to repro this by copy and paste (you're missing "query" and the scalar for UUID in your schema pasted into the question) but i get the same error regardless of whether I use GET or POST in the http resolver if I hit "run test"

you were able to get it to work with GET but not post?
Freddy Martinez Garcia 0 Reputation points

2023-11-29T03:22:16.47+00:00
Thanks for your answer @Ben Gimblett

Yes, I was able to make it works with a GET request, but using a different policy, here it is:

We tried something similar but using <set-body> element, and it didn’t work

Freddy Martinez Garcia 0

Sorry @Ben Gimblett I made a mistake typing the XML in my last message, here it is:

<http-data-source>
	<http-request>
		<set-method>GET</set-method>
		<set-url>@($"Azure Function URL&amp;messageId={context.GraphQL.Arguments["input"]["messageId"]}&amp;senderUserId={context.GraphQL.Arguments["input"]["senderUserId"]}&amp;receiverUserId={context.GraphQL.Arguments["input"]["receiverUserId"]}&amp;messageContent={context.GraphQL.Arguments["input"]["messageContent"]}")</set-url>
	</http-request>
</http-data-source>

Benjamin Rengifo Rodriguez 0

Hi, i have the same problem and schema is

type Group {
  id: Int
  code: String
  name: String
}

type QueryData {
  groups: [Group!]!
}

type Mutation {
    createGroup(input:Group):Int
    createGroupTwo(code:String, name:String):Int
}

schema {
  query: QueryData
  mutation: Mutation
}

and testing with resolver

<http-data-source>
	<http-request>
		<set-method>POST</set-method>
		<set-url>https://URI_POST</set-url>
		<set-body>{  
            "code": "12334",
            "name": "Benjamin"
    }</set-body>
	</http-request>
</http-data-source>

In trace Body not found and get REST response HTTP CODE 400 Bad Request

1 answer

Your answer

Ben Gimblett 4,560 Reputation points Microsoft Employee

2023-11-24T15:21:34+00:00

Hi - I've tried to repro this by copy and paste (you're missing "query" and the scalar for UUID in your schema pasted into the question) but i get the same error regardless of whether I use GET or POST in the http resolver if I hit "run test"

you were able to get it to work with GET but not post?
Freddy Martinez Garcia 0 Reputation points

2023-11-29T03:22:16.47+00:00

Thanks for your answer @Ben Gimblett

Yes, I was able to make it works with a GET request, but using a different policy, here it is:

We tried something similar but using <set-body> element, and it didn’t work
Freddy Martinez Garcia 0 Reputation points

2023-11-29T03:29:04.1866667+00:00

Sorry @Ben Gimblett I made a mistake typing the XML in my last message, here it is:

<http-data-source> <http-request> <set-method>GET</set-method> <set-url>@($"Azure Function URL&messageId={context.GraphQL.Arguments["input"]["messageId"]}&senderUserId={context.GraphQL.Arguments["input"]["senderUserId"]}&receiverUserId={context.GraphQL.Arguments["input"]["receiverUserId"]}&messageContent={context.GraphQL.Arguments["input"]["messageContent"]}")</set-url> </http-request> </http-data-source>
Benjamin Rengifo Rodriguez 0 Reputation points

2023-12-13T11:42:11.61+00:00

Hi, i have the same problem and schema is

type Group { id: Int code: String name: String } type QueryData { groups: [Group!]! } type Mutation { createGroup(input:Group):Int createGroupTwo(code:String, name:String):Int } schema { query: QueryData mutation: Mutation }

and testing with resolver

<http-data-source> <http-request> <set-method>POST</set-method> <set-url>https://URI_POST</set-url> <set-body>{ "code": "12334", "name": "Benjamin" }</set-body> </http-request> </http-data-source>

In trace Body not found and get REST response HTTP CODE 400 Bad Request

Answer 1

JananiRamesh-MSFT 29,276

@Freddy Martinez Garcia Thanks for reaching out. As per the investigation we identified below two issues.

HTTP resolver with set-body - Request set-body policy not invoked in http-data-source. It does affect the same scenario that the older issue was describing in this pos, so it is a regression. That is, the old issue was fixed, however the functionality there regressed in a different manner, due to another bug.
Resolver testing UI - Fails with Internal Server Error when using generic notation (eg. As<JObject>()) in set-body

Our product team is working on the fix, No ETA available as of now. Would recommend you track update in https://github.com/Azure/API-Management/releases.

We apologize for the inconvenience caused by the issue. Feel free to add a comment if any questions.

Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.

Freddy Martinez Garcia 0 Reputation points

2023-11-29T03:34:54.1033333+00:00

Hi @JananiRamesh-MSFT thanks for your answer. Does that mean that I can’t configure the resolver to make a POST request instead a GET request? cause if you say that the previous issue was fixed with a different approach, it means that there is a different work around to make a POST request in the resolver configuration.

Am I correct? and if so, can you point me in the right direction please?

Regards
JananiRamesh-MSFT 29,276 Reputation points

2023-11-29T16:35:38.25+00:00

Freddy Martinez Garcia Thanks for getting back.

The Workaround for Issue #1. you can use the following in your set-body.

var args = context.GraphQL.Arguments

please try and let me know if it works.

Share via

Unable to use Resolver Policy in a Graphql Resolver for POST http calls

1 answer

Your answer