-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release: v0.1.0-alpha.7 #551
Conversation
- Adds `CHANGELOG.md` entries for everything since `v0.1.0-alpha.6` - Bumps versions in `Cargo.toml` files (and licensing related bits in `cargo-deny.toml`)
[Managed Federation]: https://www.apollographql.com/docs/federation/managed-federation/overview/ | ||
|
||
The Router can now automatically download and check for updates on its schema from Studio (via [Uplink])'s free, [Managed Federation] service. This is configured in the same way as Apollo Gateway via the `APOLLO_KEY` and `APOLLO_GRAPH_REF` environment variables, in the same way as was true in Apollo Gateway ([seen here](https://www.apollographql.com/docs/federation/managed-federation/setup/#4-connect-the-gateway-to-studio)). This will also enable operation usage reporting. | ||
|
||
> **Note:** It is not yet possible to configure the Router with [`APOLLO_SCHEMA_CONFIG_DELIVERY_ENDPOINT`]. If you need this behavior, please open a feature request with your use case. | ||
|
||
[Managed Federation]: https://www.apollographql.com/docs/federation/managed-federation/overview/ | ||
[`APOLLO_SCHEMA_CONFIG_DELIVERY_ENDPOINT`]: https://www.apollographql.com/docs/federation/managed-federation/uplink/#environment-variable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've opted to stop using this convenient reference pattern since GitHub flavored markdown doesn't have a notion of scope (e.g., [Ref]
s apply to the whole file and the first [Ref]
wins).
Note I haven't completely eradicated its use yet though.
me = 😢 🐼
Perf test please |
Signed-off-by: Benjamin Coenen <5719034+bnjjj@users.noreply.github.com>
Perf test please |
Perf test please |
1 similar comment
Perf test please |
✨ Features
Apollo Studio Explorer landing page (PR #526)
We've replaced the redirect to Apollo Studio with a statically rendered landing page. This supersedes the previous redirect approach was merely introduced as a short-cut. The experience now duplicates the user-experience which exists in Apollo Gateway today.
It is also possible to save the redirect preference and make the behavior sticky for future visits. As a bonus, this also resolves the failure to preserve the correct HTTP scheme (e.g.,
https://
) in the event that the Apollo Router was operating behind a TLS-terminating proxy, since the redirect is now handled client-side.Overall, this should be a more durable and more transparent experience for the user.
Display Apollo Router version on startup (PR #543)
The Apollo Router displays its version on startup from now on, which will come in handy when debugging/observing how your application behaves.
🐛 Fixes
Passing a
--supergraph
file supersedes Managed Federation (PR #535)The
--supergraph
flag will no longer be silently ignored when the Supergraph is already being provided through Managed Federation (i.e., when theAPOLLO_KEY
andAPOLLO_GRAPH_REF
environment variables are set). This allows temporarily overriding the Supergraph schema that is fetched from Apollo Studio's Uplink endpoint, while still reporting metrics to Apollo Studio reporting ingress.Anonymous operation names are now empty in tracing (PR #525)
When GraphQL operation names are not necessary to execute an operation (i.e., when there is only a single operation in a GraphQL document) and the GraphQL operation is not named (i.e., it is anonymous), the
operation_name
attribute on the trace spans that are associated with the request will no longer contain a single hyphen character (-
) but will instead be an empty string. This matches the way that these operations are represented during the GraphQL operation's life-cycle as well.Resolved missing documentation in Apollo Explorer (PR #540)
We've resolved a scenario that prevented Apollo Explorer from displaying documentation by adding support for a new introspection query which also queries for deprecation (i.e.,
includeDeprecated
) oninput
arguments.