Push up changelog

CHANGELOG.md

@@ -16,6 +16,21 @@ The version headers in this history reflect the versions of Apollo Server itself
     - The federated tracing plugin's `ftv1` response on `extensions` (which is present on the response from an implementing service to the gateway) is now placed on the `extensions` _after_ the `formatResponse` hook.  Anyone leveraging the `extensions`.`ftv1` data from the `formatResponse` hook will find that it is no longer present at that phase.
 - `apollo-tracing`: This package's internal integration with Apollo Server has been switched from using the soon-to-be-deprecated`graphql-extensions` API to using [the request pipeline plugin API](https://www.apollographql.com/docs/apollo-server/integrations/plugins/).  Behavior should remain otherwise the same.  [PR #3991](https://github.com/apollographql/apollo-server/pull/3991)
 
+- `apollo-engine-reporting`: Added an experimental schema reporting feature to engine reporting. Previously the only way to get schemas into the schema registry in Apollo Graph Manager, was to use the cli and run `apollo schema:push`. _Apollo schema reporting protocol_, is a *new* specification for GraphQL servers to automatically report schemas to the Apollo Graph Manager schema registry.
+
+    - To enable schema reporting provide a Graph Manager API key (available from [Apollo Graph Manager](https://engine.apollographql.com/)) in the `APOLLO_KEY` environment variable *and* set the `experimental_schemaReporting` option to `true` in the Apollo Server constructor options, like so:
+    ```js
+    const server = new ApolloServer({
+      typeDefs,
+      resolvers,
+      engine: {
+        experimental_schemaReporting: true,
+        /* Other existing options can remain the same. */
+      },
+    });
+    ```
+  - When enabled, a schema reporter is initiated by the `apollo-engine-reporting` agent.  It will loop until the `ApolloServer` instance is stopped, periodically calling back to Apollo Graph Manager to send information.  The life-cycle of this reporter is managed by the agent.
+
 ### v2.13.0
 
 > [See complete versioning details.](https://github.com/apollographql/apollo-server/commit/e37384a49b2bf474eed0de3e9f4a1bebaeee64c7)

docs/source/api/apollo-server.md

@@ -404,7 +404,7 @@ addMockFunctionsToSchema({
 
     - `{ none: true }`: Don't send any variable values. **(DEFAULT)**
     - `{ all: true }`: Send all variable values.
-    - `{ transform: ({ variables, operationString}) => { ... } }`: A custom function for modifying variable values. Keys added by the custom function will be removed, and keys removed will be added back with an empty value.  For security reasons, if an error occurs within this function, all variable values will be replaced with `[PREDICATE_FUNCTION_ERROR]`. 
+    - `{ transform: ({ variables, operationString}) => { ... } }`: A custom function for modifying variable values. Keys added by the custom function will be removed, and keys removed will be added back with an empty value.  For security reasons, if an error occurs within this function, all variable values will be replaced with `[PREDICATE_FUNCTION_ERROR]`.
     - `{ exceptNames: [...] }`: A case-sensitive list of names of variables whose values should not be sent to Apollo servers.
     - `{ onlyNames: [...] }`: A case-sensitive list of names of variables whose values will be sent to Apollo servers.
 
@@ -472,8 +472,14 @@ addMockFunctionsToSchema({
 
 *  `schemaTag`: String
 
+   > Will be deprecated in 3.0. Use the option `graphVariant` instead.
+
    A human-readable name to tag this variant of a schema (i.e. staging, EU). Setting this value will cause metrics to be segmented in the Apollo Platform's UI. Additionally schema validation with a schema tag will only check metrics associate with the same string.
 
+*  `graphVariant`: String
+
+   A human-readable name for the variant of a schema (i.e. staging, EU). Setting this value will cause metrics to be segmented in the Apollo Graph Manager UI. Additionally schema validation with a graph variant will only check metrics associate with the same string.
+
 *  `generateClientInfo`: (GraphQLRequestContext) => ClientInfo **AS 2.2**
 
    Creates a client context(ClientInfo) based on the request pipeline's