DeGraphQL

This plugin transforms a GraphQL upstream into a traditional endpoint by mapping uris into GraphQL queries.

Terminology

• plugin: a plugin executing actions inside Kong before or after a request has been proxied to the upstream API.
• Service: the Kong entity representing an external upstream API or microservice.
• upstream service: this refers to your own API/service sitting behind Kong, to which client requests are forwarded.

Configuration

Enabling the plugin on a Service

Configure this plugin on a Service by making the following request:

$ curl -X POST http://kong:8001/services/{service}/plugins \
    --data "name=degraphql" 

{service} is the id or name of the Service that this plugin configuration will target.

Global plugins

• Using a database, all plugins can be configured using the http://kong:8001/plugins/ endpoint.
• Without a database, all plugins can be configured via the plugins: entry on the declarative configuration file.

A plugin which is not associated to any Service, Route or Consumer (or API, if you are using an older version of Kong) is considered "global", and will be run on every request. Read the Plugin Reference and the Plugin Precedence sections for more information.

Parameters

Here's a list of all the parameters which can be used in this plugin's configuration:

Usage

DeGraphQL needs a graphql endpoint to query. As an example, we are going to build a REST API around https://api.github.com GraphQL service. For that reason examples are going to include the header Authorization: Bearer some-token.

Note this plugin differs from other plugins as far as configuration goes. It needs to be activated on a service that points to a GraphQL endpoint (sans /graphql).

1. Create a Service and a Route in Kong:

  $ curl -X POST http://localhost:8001/services \
    --data name="github" \
    --data url="https://api.github.com"
  $ curl -X POST http://localhost:8001/services/github/routes \
    --data paths="/api"

2. Configure the Plugin on the Service

The plugin takes over the service. From this point on, the service represents our REST api and not the graphql endpoint itself. It will return a 404 Not Found if no DeGraphQL routes have been configured.

  $ curl -X POST http://localhost:8001/services/github/plugins \
    --data name="degraphql"

3. Configure DeGraphQL Routes on the Service

Once the Plugin is activated on a Service, we can add our own routes to build our service, by defining uris and associating them to GraphQL queries.

  $ curl -X POST http://localhost:8001/services/github/degraphql/routes \
    --data uri="/me" \
    --data query="query { viewer { login } }"

  $ curl http://localhost:8000/api/me \
    --header "Authorization: Bearer some-token"
  {
      "data": {
          "viewer": {
              "login": "you"
          }
      }
  }

GraphQL Query Variables can be defined on uris

  $ curl -X POST http://localhost:8001/services/github/degraphql/routes \
    --data uri='/:owner/:name' \
    --data query='query ($owner:String! $name:String!){
                    repository(owner:$owner, name:$name) {
                      name
                      forkCount
                      description
                   }
                 }'

  $ curl http://localhost:8000/api/kong/kong \
    --header "Authorization: Bearer some-token"
  {
    "data": {
        "repository": {
            "description": "🦍 The Cloud-Native API Gateway ",
            "forkCount": 2997,
            "name": "kong"
        }
    }
  }

The same Variables can also be provided as GET arguments

  $ curl -X POST http://localhost:8001/services/github/degraphql/routes \
    --data uri='/repo' \
    --data query='query ($owner:String! $name:String!){
                    repository(owner:$owner, name:$name) {
                      name
                      forkCount
                      description
                    }
                  }'

  $ curl "http://localhost:8000/api/repo?owner=kong&name=kuma" \
    --header "Authorization: Bearer some-token"
  {
    "data": {
        "repository": {
            "description": "🐻 The Universal Service Mesh",
            "forkCount": 48,
            "name": "kuma"
        }
    }
  }

Available endpoints

List defined DeGraphQL Routes for a service

Create a DeGraphQL Route for a Service

Edit a DeGraphQL Route for a Service

Delete a DeGraphQL Route for a Service