v0.1.0-preview.4

❗ BREAKING ❗

• Telemetry simplification PR #782

  Telemetry configuration has been reworked to focus exporters rather than OpenTelemetry. Users can focus on what they are trying to integrate with rather than the fact that OpenTelemetry is used in the Apollo Router under the hood.

  telemetry:
    apollo:
      endpoint:
      apollo_graph_ref:
      apollo_key:
    metrics:
      prometheus:
        enabled: true
    tracing:
      propagation:
        # Propagation is automatically enabled for any exporters that are enabled,
        # but you can enable extras. This is mostly to support otlp and opentracing.
        zipkin: true
        datadog: false
        trace_context: false
        jaeger: false
        baggage: false
  
      otlp:
        endpoint: default
        protocol: grpc
        http:
          ..
        grpc:
          ..
      zipkin:
        agent:
          endpoint: default
      jaeger:
        agent:
          endpoint: default
      datadog:
        endpoint: default

🚀 Features

• Datadog support PR #782

  Datadog support has been added via telemetry yaml configuration.

• Yaml env variable expansion PR #782

  All values in the router configuration outside the server section may use environment variable expansion.
  Unix style expansion is used. Either:

  • ${ENV_VAR_NAME}- Expands to the environment variable ENV_VAR_NAME.
  • ${ENV_VAR_NAME:some_default} - Expands to ENV_VAR_NAME or some_default if the environment variable did not exist.

  Only values may be expanded (not keys):

  example:
    passord: "${MY_PASSWORD}" 

🐛 Fixes

• Accept arrays in keys for subgraph joins PR #822

  The router is now accepting arrays as part of the key joining between subgraphs.

• Fix value shape on empty subgraph queries PR #827

  When selecting data for a federated query, if there is no data the router will not perform the subgraph query and will instead return a default value. This value had the wrong shape and was generating an object where the query would expect an array.

🛠 Maintenance

• Apollo federation 2.0.0 compatible query planning PR#828

  Now that Federation 2.0 is available, we have updated the query planner to use the latest release (@apollo/query-planner v2.0.0).