-
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
prep release: v1.14.0 #2911
Merged
Merged
prep release: v1.14.0 #2911
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
abernix
requested review from
a team,
Geal,
SimonSapin,
BrynCooke,
bnjjj and
o0Ignition0o
and removed request for
SimonSapin and
BrynCooke
April 6, 2023 17:35
o0Ignition0o
reviewed
Apr 6, 2023
o0Ignition0o
approved these changes
Apr 6, 2023
Merged
bnjjj
approved these changes
Apr 7, 2023
Geal
approved these changes
Apr 7, 2023
|
||
Our Helm chart now supports a new value called `extraLabels`, which enables chart users to add custom labels to the Router Deployment and its Pods. | ||
|
||
By [@gscheibel(https://github.com/gscheibel/) in https://github.com/apollographql/router/pull/2903 |
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.
Suggested change
By [@gscheibel(https://github.com/gscheibel/) in https://github.com/apollographql/router/pull/2903 | |
By [@gscheibel](https://github.com/gscheibel/) in https://github.com/apollographql/router/pull/2903 |
|
||
Our Helm chart now supports `extraContainers` in an effort to simplify the ability to run containers alongside Router containers (sidecars) which is a useful pattern for [coprocessors](https://www.apollographql.com/docs/router/customizations/coprocessor/). | ||
|
||
By [@pcarrier(https://github.com/pcarrier) in https://github.com/apollographql/router/pull/2881 |
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.
Suggested change
By [@pcarrier(https://github.com/pcarrier) in https://github.com/apollographql/router/pull/2881 | |
By [@pcarrier](https://github.com/pcarrier) in https://github.com/apollographql/router/pull/2881 |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🚀 Features
GraphOS Enterprise: Coprocessor read access to request
uri
,method
and HTTP response status codes (Issue #2861, Issue #2861)We've added the ability for coprocessors to have read-only access to additional contextual information at the
RouterService
andSubgraphService
stages:The
RouterService
stage now has read-only access to the request from the client:path
(e.g.,/graphql
)method
(e.g.,POST
,GET
)The
RouterService
stage now has read-only access to the overall response to the client:status_code
(e.g.403
,200
)The
SubgraphService
stage now has read-only access to the response of the subgraph request:status_code
(e.g.,503
,200
)By @o0ignition0o in #2863
🐛 Fixes
Coprocessors: Empty body requests from
GET
requests are now deserialized without errorFixes a bug where a coprocessor operating at the
router_request
stage would fail to deserialize an empty body, which is typical forGET
requests.By @o0ignition0o in #2863
📃 Configuration
Helm: Router chart now supports
extraLabels
for Deployments/PodsOur Helm chart now supports a new value called
extraLabels
, which enables chart users to add custom labels to the Router Deployment and its Pods.By [@gscheibel(https://github.com/gscheibel/) in https://github.com//pull/2903
Helm: Router chart now supports
extraContainers
to run sidecarsOur Helm chart now supports
extraContainers
in an effort to simplify the ability to run containers alongside Router containers (sidecars) which is a useful pattern for coprocessors.By [@pcarrier(https://github.com/pcarrier) in https://github.com//pull/2881
Migrate away from unimplemented
coprocessor.subgraph.all.response.uri
We have removed a completely unimplemented
coprocessor.subgraph.all.response.uri
key from our configuration. It had no effect, but we will automatically migrate configurations which did use it, resulting in no breaking changes by this removal.By @o0ignition0o in #2863
📚 Documentation
Update coprocessor documentation to reflect newly added fields (Issue #2886)
The External coprocessing documentation is now up to date, with a full configuration example, and the newly added fields.
By @o0Ignition0o in #2863
Example: Rhai-based
cache-control
response header managementA new Rhai example demonstrates how to recreate some of the behavior of Apollo Gateway's subgraph
cache-control
response header behavior. This addresses some of the need identified in #326.By @lennyburdette in #2759