chore(deps): update ghcr.io/apollographql/router docker tag to v1.24.0 #184
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.23.0
->v1.24.0
Release Notes
apollographql/router (ghcr.io/apollographql/router)
v1.24.0
Compare Source
🚀 Features
Add support for delta aggregation to otlp metrics (PR #3412)
Add a new configuration option (Temporality) to the otlp metrics configuration.
This may be useful to fix problems with metrics when being processed by datadog which tends to expect Delta, rather than Cumulative, aggregations.
See:
for more details.
By @garypen in https://github.com/apollographql/router/pull/3412
🐛 Fixes
Fix error handling for subgraphs (Issue #3141)
The GraphQL spec is rather light on what should happen when we process responses from subgraphs. The current behaviour within the Router was inconsistently short circuiting response processing and this producing confusing errors.
The logic has been simplified and made consistent using the following rules:
application/json
orapplication/graphql-response+json
then we won't try to parse.application/json
and status is not 2xx and the body is not valid grapqhql the entire subgraph response will be attached as an error.By @BrynCooke in https://github.com/apollographql/router/pull/3328
🛠 Maintenance
chore: router-bridge 0.3.0+v2.4.8 -> =0.3.1+2.4.9 (PR #3407)
Updates
router-bridge
from= "0.3.0+v2.4.8"
to= "0.3.1+v2.4.9"
, note that with this PR, this dependency is now pinned to an exact version. This version update started failing tests because of a minor ordering change and it was not immediately clear why the test was failing. Pinning this dependency (that we own) allows us to only bring in the update at the proper time and will make test failures caused by the update to be more easily identified.By @EverlastingBugstopper in https://github.com/apollographql/router/pull/3407
remove the compiler from Query (Issue #3373)
The
Query
object caches information extracted from the query that is used to format responses. It was carrying anApolloCompiler
instance, but now we don't really need it anymore, since it is now cached at the query analysis layer. We also should not carry it in the supergraph request and execution request, because that makes the builders hard to manipulate for plugin authors. Since we are not exposing the compiler in the public API yet, we move it inside the context's private entries, where it will be easily accessible from internal code.By @Geal in https://github.com/apollographql/router/pull/3367
move AllowOnlyHttpPostMutationsLayer at the supergraph service level (PR #3374, PR #3410)
Now that we have access to a compiler in supergraph requests, we don't need to look into the query plan to know if a request contains mutations
By @Geal in https://github.com/apollographql/router/pull/3374 & https://github.com/apollographql/router/pull/3410
update opentelemetry to 0.19.0 (Issue #2878)
We've updated the following opentelemetry related crates:
This allows us to close a number of opentelemetry related issues.
Note:
The prometheus specification mandates naming format and, unfortunately, the router had two metrics which weren't compliant. The otel upgrade enforces the specification, so the affected metrics are now renamed (see below).
The two affected metrics in the router were:
apollo_router_cache_hit_count -> apollo_router_cache_hit_count_total
apollo_router_cache_miss_count -> apollo_router_cache_miss_count_total
If you are monitoring these metrics via prometheus, please update your dashboards with this name change.
By @garypen in https://github.com/apollographql/router/pull/3421
Synthesize defer labels without RNG or collisions (PR #3381 and PR #3423)
The
@defer
directive accepts alabel
argument, but it is optional. To more accurately handle deferred responses, the Router internally rewrites queries to add labels on the@defer
directive where they are missing. Responses eventually receive the reverse treatment to look as expected by client.This was done be generating random strings, handling collision with existing labels, and maintaining a
HashSet
of which labels had been synthesized. Instead, we now add a prefix to pre-existing labels and generate new labels without it. When processing a response, the absence of that prefix indicates a synthetic label.By @SimonSapin and @o0Ignition0o in https://github.com/apollographql/router/pull/3381 and https://github.com/apollographql/router/pull/3423
Move subscription event execution at the execution service level (PR #3395)
In order to prepare some future integration I moved the execution loop for subscription events at the execution_service level.
By @bnjjj in https://github.com/apollographql/router/pull/3395
📚 Documentation
Document claim augmentation via coprocessors (Issue #3102)
Claims augmentation is a common use case where user information from the JWT claims is used to look up more context like roles from databases, before sending it to subgraphs. This can be done with subgraphs, but it was not documented yet, and there was confusion on the order in which the plugins were called. This clears the confusion and provides an example configuration.
By @Geal in https://github.com/apollographql/router/pull/3386
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.