v0.2.4

What's Changed

• Support application/x-ndjson response content type by @hgiasac in #19
• upgrade ndc-sdk-go v1.3.0 by @hgiasac in #20

Full Changelog: v0.2.3...v0.2.4

v0.2.3

What's Changed

• feat: apply default headers from settings by @hgiasac in #17
• feat: upgrade ndc-rest-schema v0.2.2 by @hgiasac in #18

Full Changelog: v0.2.2...v0.2.3

v0.2.2

What's Changed

• inject trace headers to incoming requests and improve distributed docs by @hgiasac in #15
• upgrade dependencies by @hgiasac in #16

Full Changelog: v0.2.1...v0.2.2

v0.2.1

What's Changed

• Upgrade ndc-rest-schema v0.2.1 by @hgiasac in #12
• Deprecate the convert command. You should install and use ndc-rest-schema binary directly.
• misc: change default config directory to /etc/connector by @hgiasac in #13
• fix: avoid modifying mutable request endpoints by @hgiasac in #14

Full Changelog: v0.2.0...v0.2.1

v0.2.0

Highlights

Distributed execution

Imagine that your backend have many server replications, or multiple applications with different credentials. You want to:

• Specify the server where the request will be executed to.
• Execute an operation to all servers.

For example, with below server settings, the connector will replicate existing operations with Distributed suffixes:

settings:
  servers:
    - id: dog
      url: "http://localhost:3000"
      securitySchemes:
        api_key:
          type: apiKey
          value: "dog-secret"
          in: header
          name: api_key
    - id: cat
      url: "http://localhost:3001"
      securitySchemes:
        api_key:
          type: apiKey
          value: "cat-secret"
          in: header
          name: api_key

{
  "functions": [
    {
      "arguments": {
        "restOptions": {
          "type": {
            "type": "nullable",
            "underlying_type": {
              "name": "RestSingleOptions",
              "type": "named"
            }
          }
        }
      },
      "name": "findPets",
      "result_type": {
        "element_type": {
          "name": "Pet",
          "type": "named"
        },
        "type": "array"
      }
    },
    {
      "arguments": {
        "restOptions": {
          "type": {
            "type": "nullable",
            "underlying_type": {
              "name": "RestDistributedOptions",
              "type": "named"
            }
          }
        }
      },
      "name": "findPetsDistributed",
      "result_type": {
        "name": "FindPetsDistributedResult",
        "type": "named"
      }
    }
  ]
}

RestSingleOptions object type is added to existing operations (findPets). API consumers can specify the server to be executed. If you want to execute all remote servers in sequence or parallel, findPetsDistributed function should be used.

Config schema changes

Reuse the config schema of ndc-rest-schema. There is a breaking change in the field name path -> file .

What's Changed

• Support distributed execution strategies by @hgiasac in #11
• Upgrade ndc-rest-schema v0.2.0 and NDC spec v0.1.3 by @hgiasac in #11
• Improve parameter decoding and application/x-www-form-urlencoded content type by @hgiasac in #11

Full Changelog: v0.1.3...v0.2.0

v0.1.3

What's Changed

• upgrade ndc-rest-schema v0.1.3 by @hgiasac in #10

Full Changelog: v0.1.2...v0.1.3

v0.1.2

What's Changed

• bump ndc-rest-schema v0.1.2 by @hgiasac in #9

Full Changelog: v0.1.1...v0.1.2

v0.1.1

What's Changed

• Support timeout and retry settings by @hgiasac in #8

Full Changelog: v0.1.0...v0.1.1

v0.1.0

What's Changed

• Support env template and basic authentication by @hgiasac in #1
• support server url env template and enum by @hgiasac in #2
• Update more scalars and request by @hgiasac in #4

New Contributors

• @hgiasac made their first contribution in #1

Full Changelog: https://github.com/hasura/ndc-rest/commits/v0.1.0